Cannot install CRA due to scoped module @timer/detect-port

[justinireland]

I am unable to generate a CRA since PR 2147 due to use of a scoped package @timer/detect-port with react-scripts. I am using (without option) a custom npm registry that does not support scoped modules.

Is there any way around this? It seems like this was a temporary workaround but as I am working from a heavily restricted environment I am unable to use CRA until this dependency is removed.

[gaearon]

@Timer Let's republish it under some different name? It’s kinda annoying that we keep hitting this.

Although it’s impossible to keep working around this forever. Scoped packages are an npm feature, and eventually some dependency’s dependency will start depending on them.

[Timer]

Yeah, we should just republish this under a different alias. I didn't realize the ecosystem was so behind on scoped packages. PR incoming.

[dnbkr]

Hi,

This issue is closed, but the current version of CRA is still using @timer/detect-port - I see a fork, but don't see a PR? Is there a hold up? Should we re-open the issue? Apologies if I've missed something

I'm running CRA 1.3.1

EDIT: I see what's happened; you've changed from using the scoped package, but there hasn't been a release to the CRA npm registry yet. Would you be able to do a patch release (1.3.2) or is the project not in a state to do that at the moment?

[gaearon]

Fixed in 1.0.8 (of react-scripts, not CRA itself). Please verify.
https://github.com/facebookincubator/create-react-app/releases/tag/v1.0.8

[dnbkr]

This works now behind our proxy npm mirror - thanks for that!