#107986Streamline node-version with shipped npm version
Description
Problem/Description
my scenario: I use DDEV to contribute to TYPO3 core. The perfect way is to set the node version with DDEV’s node version option flag. DDEV takes care of activating/installing the configured nodejs version automatically. However our actual version constraints (which is node 22 and a specific npm version) are not in line with the default npm-version nodejs version 22 ships.
ToDo(s)
- Check whether there are good reasons to stick to a npm version which is not the default for the required nodejs version
- Update the npm version constraint to support the default npm version which is shipped with node 22
- Use the default npm version of node 24 if we switch from node 22 to 24 with the TYPO3 v14 LTS release
be aware
There are some documentation tasks if the core team decides to not adjust version constraint of npm to the default shipped npm version. I have discussed them with the DDEV dev team and there is already an issue on GitHub. We have to adopt the contribution guide to add those somehow complicated tasks for people who want to contribute to JS/CSS stuff in the TYPO3 core.
Acceptance Criteria
I would go for a relaxed npm version constraint and stick to the nodejs defaults – no matter if node.js 22 or 24 get’s used in TYPO3 14 LTS release.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
History 3
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-11-05T19:10:59+00:00" > 11/05/25, 19:10 </span>
-
Georg Ringer changed Related to #109368 <span data-processor="relativetime" data-value="2026-10-03T19:30:46+00:00" > 10/03/26, 19:30 </span>
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-10-03T19:30:58+00:00" > 10/03/26, 19:30 </span>imo fixed with #109368
$0.02:
I think our core dev team can only support one stable platform, and this is “runTests.sh” for us. This is the only way we have images and setups under control and can run distinct environments for creating CSS/JS assets or other things in core.
I don’t think we should invest time in supporting other possibilities “officially” because runTests.sh is also what runs in our CI pipeline and has proven very stable, and is fully documented. Fragmenting the platform base will create trouble for us without a clear benefit.
ddev users already have docker available. Executing runTests.sh should be very easy for them on their host system…