Comments (19)
Please provide online reproduction, not just error messages, that doesn't help.
from commitlint.
@moran-inadvantag I don't think we support legacy node v14, node v18+ is required.
from commitlint.
The warning is occurred on installation AFAIK.
from commitlint.
Our repo is seeing this issue as well on the latest release. Hopefully this is what you mean by online repo.
I have created a public repo that shows the issue:
https://github.com/moran-inadvantage/commit_lint_issue_3950
Here is an example of the failure:
https://github.com/moran-inadvantage/commit_lint_issue_3950/actions/runs/8287030551/job/22678414864
You can trigger a workflow that fails here:
https://github.com/moran-inadvantage/commit_lint_issue_3950/actions/workflows/commit-validate.yml
from commitlint.
node v18+ is required.
Maybe we should detect the version before running, and fail fast in case it's too old?
from commitlint.
Maybe we should detect the version before running, and fail fast in case it's too old?
Something like this? https://gist.github.com/knocte/f78f8f60800e54bce59110138389105b
from commitlint.
Maybe we should detect the version before running, and fail fast in case it's too old?
Something like this? https://gist.github.com/knocte/f78f8f60800e54bce59110138389105b
@escapedcat @JounQin what do you guys think?
from commitlint.
Hmm... Didn't engines
field warning about the incompatible usage? I'm not sure whether we need to check it another time.
from commitlint.
Hmm... Didn't engines field warning about the incompatible usage? I'm not sure whether we need to check it another time.
If that was the case, wouldn't @moran-inadvantage have got a different error?
from commitlint.
This is the error you get when you install it with a wrong version:
user@machine ~/test npm install --save-dev @commitlint/{cli,config-conventional}
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@commitlint/[email protected]',
npm WARN EBADENGINE required: { node: '>=v18' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@commitlint/[email protected]',
npm WARN EBADENGINE required: { node: '>=v18' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@commitlint/[email protected]',
npm WARN EBADENGINE required: { node: '>=v18' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@commitlint/[email protected]',
npm WARN EBADENGINE required: { node: '>=v18' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@commitlint/[email protected]',
npm WARN EBADENGINE required: { node: '>=v18' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@commitlint/[email protected]',
npm WARN EBADENGINE required: { node: '>=v18' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@commitlint/[email protected]',
npm WARN EBADENGINE required: { node: '>=v18' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16.17' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@commitlint/[email protected]',
npm WARN EBADENGINE required: { node: '>=v18' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
...
I think this should be enough, no?
from commitlint.
So @moran-inadvantage didn't get this because he used it directly via npx
instead of installing?
from commitlint.
Yeah, that could be the case:
user@machine ~/test npx @commitlint/cli
@commitlint/[email protected] - Lint your commit messages
[input] reads from stdin if --edit, --env, --from and --to are omitted
Options:
-c, --color toggle colored output [boolean] [default: true]
-g, --config path to the config file
...
from commitlint.
So we need the "Unsupported engine" checks at runtime too, not just installation time.
from commitlint.
Ah no, same. Forgot to delete the node_modules
in my test
folder...
user@machine ~/test npx @commitlint/cli
Need to install the following packages:
@commitlint/cli
Ok to proceed? (y) y
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@commitlint/[email protected]',
npm WARN EBADENGINE required: { node: '>=v18' },
npm WARN EBADENGINE current: { node: 'v16.14.0', npm: '8.3.1' }
npm WARN EBADENGINE }
from commitlint.
Related Issues (20)
- chore: publish new version of @commitlint/read package HOT 2
- v19 gives `@commitlint/config-conventional` with yarn pnp HOT 18
- Module not found HOT 4
- Enable canary release for real-world testing before final release HOT 3
- fix: error TS2307: Cannot find module 'conventional-commits-parser' or its corresponding type declarations. HOT 6
- Using config example gives error running 19.0.3 HOT 22
- @commitlint/config-nx-scopes | Error [ERR_REQUIRE_ESM]: require() of ES Module Not Supported HOT 2
- Can not use @commitlint/cz-commitlint as commitizen's adapter HOT 5
- fix: console show DeprecationWarning info when use @commitlint\[email protected]
- wrapper.mjs is not included in published @commitlint/config-conventional package HOT 11
- fix(conventional): should not allow scope with dash inside HOT 3
- ERR_IMPORT_ASSERTION_TYPE_MISSING with json config package
- fix: @commitlint/config-nx-scopes not working for nx since version v19
- fix: `commitlint --last` fails HOT 2
- commitlint --edit does not change commit message once you enter a invalid commit message
- fix: Docs missing `issuePrefixes` HOT 3
- feat: <Badge for using commitlint in your repo> HOT 2
- refactor: switch from chalk to styleText (node:util) HOT 4
- feature: add flag to enable/disable multiple-scopes (default: enabled) HOT 13
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from commitlint.