Running npm init stryker use default npm registry instead of the one configured in npm config

[Tamir-M]

Summary

When running npm init stryker in air-gapped network (i.e. without access to the default npm registry) the setup fail with connection problem, this is caused due to stryker not using the configured npm registry (e.g. in .npmrc)

Stryker config
Not relevant

Test runner config

Not relevant

Stryker environment

• create-stryker: 8.3.0

Your Environment

software	version(s)
node	20.13.1
npm	10.5.2
Operating System	MacOS 14

[nicojs]

Thanks, it seems like a great addition.