-
-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supported node and npm versions #3577
Comments
Some dependencies already state their requirements:
|
I'm surprised that the CI doesn't report failing tests. I can see warnings like
on https://github.com/11ty/eleventy/actions/runs/12206669545 for example. (Associated with #3573 ) Looking at Release schedule version 18 of Node is still in Maintenance mode. So it could be an indicator to still use it. Currently, Eleventy's minimum version of Node is I'd like to see a failing test case before moving forward. |
@Ryuno-Ki Did you manage to have the test pass on your setup though? |
On commit d7434ab 1296 tests passed here. (Running Node v20.18.1 via Debian). Let me grab nvm. |
Same results with Node v18.20.5. |
Please note that there is a distinction between the Node versions that Eleventy supports and the Node versions supported by our devDependencies—they can be different (though that’s not ideal).
|
I would also note that Line 13 in 117e7e6
|
Test failure on Node 23 is currently filed at #3518 |
When running Maybe I'm wrong, but it looks like the culprits are: Line 2 in 117e7e6
Line 6 in 117e7e6
And when running the version above, The test
Some are not in the And if I unset eleventy/src/Util/DateGitLastUpdated.js Line 12 in 117e7e6
How abut 19.9.0? |
I’m confused where you’re getting this info, here’s the current dep graph showing the use of https://npmgraph.js.org/?q=%4011ty%2Feleventy#select=exact%3Apath-scurry%401.11.1 v1.11.1 of path-scurry node support Happy to look at any other examples you find though! |
Ah, that explains some confusion. There are two versions of rimraf here: |
One more thing here, we typically avoid putting resources into debugging odd versions of Node and typically recommend folks use an even number (where possible): https://nodejs.org/en/about/previous-releases If you feel this policy should be changed, please let me know! |
I made a change to |
KO on node v19.9.0 (linux) :
|
Operating system
Linux
Eleventy
npm test
Describe the bug
Test are failing on multiple versions of Node.js (18 and onward) using Eleventy 3.0.0
Running npm test fails for various reasons:
import { register } from "node:module
Fails on all versions of Node.js
I tested using both my machine (Node v23.1.0 and npm 10.9.1) and the Docker images: node:19-alpine to node:23-alpine.
I suggest we clarify which versions of Node are supported in the package.json file, currently it only says "Node.js v18 onward" which is obviously not the case. We could also add the supported npm version (which is not the same).
Strangely enough, the CIs all pass?
Reproduction steps
docker run -u $(id -u $USER):$(id -g $USER) -it -v './:/app' -w /app node:23-alpine sh -c 'npm ci && npm test'
Expected behavior
Tests should pass
Reproduction URL
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered: