Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

conventional-commits-parser- Node engine incompatibility

See original GitHub issue

The conventional-commits-parser supports Node > 6 but use a package called is-text-path which required Node >= 8. This produce an error at installing with yarn.

Issue Analytics

State:
Created 4 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

tommywocommented, Nov 4, 2019

I’ve downgraded is-text-path. Release is on @next tag

0reactions

StarpTechcommented, Nov 4, 2019

@tommywo thank you.

Top Results From Across the Web

conventional-commits-parser - npm

Start using conventional-commits-parser in your project by running `npm i conventional-commits-parser`. There are 293 other projects in the ...

Cannot find module 'conventional-commits-parser' #3049

Classic output. Your README doesn't mention the package is needed to run the tool. Current Behavior. node:internal/modules/cjs/ ...

How to ignore incompatible engine "node" error on installing ...

yarn config set ignore-engines true is a one time fix for the "the engine node is incompatible with this module" problem.

conventional-commits-parser | Yarn - Package Manager

Fast, reliable, and secure dependency management.

NVIDIA Deep Learning TensorRT Documentation

Since the serialized engine contains the necessary copies of the weights, the parser, network definition, builder configuration and builder are no longer ...