enhancement/issue 1379 stabilize nodejs version 22.18.0

[thescientist13]

Related Issue

resolves #1379

Documentation

1. document recommended minimum version of NodeJS - document latest NodeJS LTS / minimum version support (22.18.0) www.greenwoodjs.dev#226

Summary of Changes

1. Update GitHub Actions, .nvmrc, engines, etc
2. Removed strip types flag from init TS scaffolding starter
3. Adopt amaro for internal type-stripping in Greenwood (instead of sucrase)

TODO

1. 🚨 Need to wait for GitHub Actions to support latest version
   • just waiting on windows now - enhancement/issue 1379 stabilize nodejs version 22.18.0 #1543 (review)
2. Greenwood <> Amaro (swap out sucrase)
3. Check adapter <> Node versions compat
   • not much we can do about 24.x support at this time - Node 24 Serverless Environment support #1533
4. WCC <> Amaro
   • I don't think, since we need Sucrase for JSX too
5. review if case "CIRCULAR_DEPENDENCY": in Rollup is still needed
   • I think this is fine for now
6. See if we can start using fs.cp + w / recursive flag - that was easy, we're already using it! 😅
7. Update PR checks to capture latest workflows after merge

Nice to have / own issues

1. See if we can start using fs.glob (still experimental) - refactor usages of glob-promise with native NodeJS fs.glob #1551
   • enhancement/issue 1379 stabilize nodejs version 22.18.0 #1543 (comment)
2. Any chance URL Pattern is available in Node 22 now? (needed for SSR and API routes should support dynamic route naming (with prerendering) #882)
   • nope, not yet, only in >= 23.8.0
3. Also, coming out of enhancement/issue 1324 prefix all node builtins imports with node: #1519, we could also consider enforcing our ESLint rule for node prefixes to match a NodeJS version.
   • I think it's fine, since we can only specify a single specific version and no ranges. But our test coverage should keep us honest here
4. We can probably adopt parseArgs for the CLI and init packages now, so should make an issue - refactor CLI command runner to use native NodeJS parseArgs utility #1552
   • that said, it doesn't handle the "nice" things like a description, wonder if we could / should just roll that on our own?
5. GitHub Actions still has a versioned ubuntu image - chore/bump linux actions to ubuntu-latest #1555

[thescientist13]

Just checked and GitHub Actions are still on 22.17.x
https://github.com/ProjectEvergreen/greenwood/actions/runs/16737214358/job/47378407422

[thescientist13]

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

[thescientist13]

For an example of how to do the fs.glob conversion

// 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);
});