Suppress deprecation warnings for create-astro

[TheOtterlord]

Changes

• Suppresses node deprecation warnings when running npm create astro
• We'll probably need to revisit our fs usage, but this is a quick fix for v24.5+

Testing

N/A

Docs

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: 04fdfa5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[bjohansebas]

I don’t feel comfortable disabling all warnings, I would prefer to use process.noDeprecation as a temporary solution.

[TheOtterlord]

Thanks! I had no idea that was settable, but it works.

[bjohansebas]

I’ve been consulting with some Node.js folks, and while there’s no way to programmatically disable the warning for a specific deprecation, we could do something like this:

process.on('warning', (warning) => {
  // Ignore a warning
  if (…)
  // Log other warnings to the console
  console.error(warning);
});

It’s probably better, since disabling all deprecations could mean a new one is added and we never know it was introduced.

[florian-lefebvre]

I would prefer fixing the actual issue rather than hiding it

[bjohansebas]

see #14219