-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install CRA due to scoped module @timer/detect-port #2481
Comments
@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. |
Yeah, we should just republish this under a different alias. I didn't realize the ecosystem was so behind on scoped packages. PR incoming. |
* Update Travis CI Node versions in User Guide (facebook#2454) Removed Node v4 (CRA only supports Node >= 6) * re-add storybook && update the documentation and links (facebook#2331) * re-add storybook && update the documentation and links * Change to new documentation domain * Prioritize index.css over the implicit App.css (facebook#2470) * Added NamedModulesPlugin in webpack.config.dev.js (facebook#2458) * Added NamedModulesPlugin in webpack.config.dev.js * Update webpack.config.dev.js * Unscope detect-port (facebook#2483) Resolves facebook#2481 * Update webpack links to point to webpack 2 (facebook#2492) * Update README.md to make links to webpack point to webpack.js.org instead insteade of webpack 1 webpack.githup.io * chore(templates): Move GitHub templates to hidden .github folder (facebook#2489) * Fix minor docs typo (facebook#2500) * Fix link to Storybook docs (facebook#2521) * Simplify flow init docs (facebook#2522) - Call `npm run flow --init` won't create a .flowconfig file, it should be `npm run flow init`
Hi, This issue is closed, but the current version of CRA is still using 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? |
Fixed in 1.0.8 (of |
This works now behind our proxy npm mirror - thanks for that! |
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.
The text was updated successfully, but these errors were encountered: