Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Closed
justinireland opened this issue Jun 6, 2017 · 5 comments
Closed

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

justinireland opened this issue Jun 6, 2017 · 5 comments

Comments

@justinireland
Copy link

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
Copy link
Contributor

gaearon commented Jun 6, 2017

@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
Copy link
Contributor

Timer commented Jun 6, 2017

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

@Timer Timer closed this as completed in dc4ce60 Jun 6, 2017
paweljedrzejczyk pushed a commit to paweljedrzejczyk/create-react-app that referenced this issue Jun 12, 2017
@backstroke-bot @paweljedrzejczyk
Update from upstream repo facebookincubator/create-react-app (#1)
16c642e 
* 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`
@dnbkr
Copy link

dnbkr commented Jun 15, 2017 •
edited
Loading

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
Copy link
Contributor

gaearon commented Jun 28, 2017 •
edited
Loading

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
Copy link

dnbkr commented Jun 29, 2017

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

romaindso pushed a commit to romaindso/create-react-app that referenced this issue Jul 10, 2017
@Timer @romaindso
Unscope detect-port (facebook#2483)
228ec9e 
Resolves facebook#2481
wmonk referenced this issue in wmonk/create-react-app-typescript Aug 7, 2017
@Timer @wmonk
Unscope detect-port (#2483)
349caa4 
Resolves #2481
@lock lock bot locked and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@justinireland @Timer @gaearon @dnbkr