enhancement/issue 1379 stabilize nodejs version 22.18.0#1543
Merged
thescientist13 merged 3 commits intoAug 21, 2025
Merged
Conversation
Member
Author
|
Just checked and GitHub Actions are still on |
thescientist13
commented
Aug 8, 2025
Member
Author
There was a problem hiding this comment.
we're so back 🚀
https://github.com/ProjectEvergreen/greenwood/actions/runs/16842547704/job/47716432732

edit: spoke to soon, seems like Windows is still on 22.17.x 😢
https://github.com/ProjectEvergreen/greenwood/actions/runs/16842547701/job/47716432741

Member
Author
|
For an example of how to do the // before
it("should contain one javascript file in the output directory", async function () {
expect(await glob.promise(path.join(this.context.publicDir, "*.js"))).to.have.lengthOf(1);
});// after
it("should contain one javascript file in the output directory", async function () {
const files = await Array.fromAsync(fs.promises.glob(
"*.js",
{ cwd: new URL(".", import.meta.url)},
));
expect(files.length).to.equal(1);
}); |
This was referenced Aug 16, 2025
thescientist13
marked this pull request as ready for review
August 16, 2025 00:54
thescientist13
force-pushed
the
enhancement/issue-1379-stabilize-nodejs-version-22.18.0
branch
from
August 21, 2025 02:05
835045d to
12d4c6a
Compare
thescientist13
deleted the
enhancement/issue-1379-stabilize-nodejs-version-22.18.0
branch
August 21, 2025 02:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Related Issue
resolves #1379
Documentation
Summary of Changes
TODO
24.xsupport at this time - Node 24 Serverless Environment support #1533case "CIRCULAR_DEPENDENCY":in Rollup is still neededfs.cp+ w / recursive flag - that was easy, we're already using it! 😅Nice to have / own issues
fs.glob(still experimental) - refactor usages of glob-promise with native NodeJSfs.glob#1551>= 23.8.0Also, coming out of enhancement/issue 1324 prefix all node builtins imports withnode:#1519, we could also consider enforcing our ESLint rule for node prefixes to match a NodeJS version.parseArgsfor the CLI and init packages now, so should make an issue - refactor CLI command runner to use native NodeJSparseArgsutility #1552