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.

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

Unable to install versions after 1.10.3 #2895

Closed
d3caf opened this issue Apr 6, 2019 · 3 comments
Closed

Unable to install versions after 1.10.3 #2895

d3caf opened this issue Apr 6, 2019 · 3 comments
Labels
🐛 Bug ✖️ Non-Parcel bug Bugs related to dependencies or plugins

Comments

@d3caf
Copy link
Contributor

d3caf commented Apr 6, 2019

🐛 bug report

I'm trying to globally install parcel@latest and am getting Couldn't find package "@parcel/fs@^1.11.0" required by "parcel@latest" on the "npm" registry.

This seems to be an issue using either NPM or Yarn to install. I tried installing parcel@1.11 but that fails with the same issue. It seems that Parcel 1.10.3 is the latest version I can get to install without getting the error.

🎛 Configuration (.babelrc, package.json, cli command)

yarn global add parcel@latest

{ 'version-tag-prefix': 'v',
  'version-git-tag': true,
  'version-commit-hooks': true,
  'version-git-sign': false,
  'version-git-message': 'v%s',
  'init-version': '1.0.0',
  'init-license': 'MIT',
  'save-prefix': '^',
  'bin-links': true,
  'ignore-scripts': false,
  'ignore-optional': false,
  registry: 'https://registry.yarnpkg.com',
  'strict-ssl': true,
  'user-agent': 'yarn/1.15.2 npm/? node/v8.11.3 darwin x64',
  lastUpdateCheck: 1554512484035 }
info npm config
{ _auth: REDACTED,
  'always-auth': true,
  email: REDACTED,
  python: '/usr/bin/python' }

🤔 Expected Behavior

Parcel should be installed

😯 Current Behavior

I get Couldn't find package "@parcel/fs@^1.11.0" required by "parcel@latest" on the "npm" registry.

[1/4] 🔍  Resolving packages...
error Couldn't find package "@parcel/fs@^1.11.0" required by "parcel@latest" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.
Error: Couldn't find package "@parcel/workers@^1.11.0" required by "parcel@latest" on the "npm" registry.
    at MessageError.ExtendableBuiltin (/usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:721:66)
    at new MessageError (/usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:750:123)
    at PackageRequest.<anonymous> (/usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:35729:17)
    at Generator.throw (<anonymous>)
    at step (/usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:304:30)
    at /usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:317:13
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
Error: Couldn't find package "@parcel/logger@^1.11.0" required by "parcel@latest" on the "npm" registry.
    at MessageError.ExtendableBuiltin (/usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:721:66)
    at new MessageError (/usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:750:123)
    at PackageRequest.<anonymous> (/usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:35729:17)
    at Generator.throw (<anonymous>)
    at step (/usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:304:30)
    at /usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:317:13
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

🌍 Your Environment

Software Version(s)
Parcel --
Node 8.11.3
npm/Yarn 1.15.2
Operating System MacOS 10.14.3
@d3caf
Copy link
Contributor Author

d3caf commented Apr 12, 2019

I think this is caused by npm/npm#19254. If I move my .npmrc -> .npmrc.bak, everything works fine.

@DeMoorJasper
Copy link
Member

DeMoorJasper commented Apr 13, 2019

@parcel/fs actually exists, it's probably an npm thing or perhaps some private package repository you are using?

Screenshot 2019-04-13 at 14 44 20

It does exist so it should work.

Please close the issue if this was the cause of the bug.

@DeMoorJasper DeMoorJasper added the ✖️ Non-Parcel bug Bugs related to dependencies or plugins label Apr 13, 2019
@d3caf
Copy link
Contributor Author

d3caf commented Apr 17, 2019

I don't have a custom registry set up currently but it seems like the presence of .npmrc is causing the issue maybe? As soon as I rename/move my .npmrc, everything installs fine. So yeah, it's either an NPM issue or a config issue on my part. I'll go ahead and close it 🙂

Here is the contents of my .npmrc for reference:

_auth=REDACTED
always-auth=true
email=REDACTED
registry=https://registry.npmjs.org

@d3caf d3caf closed this as completed Apr 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug ✖️ Non-Parcel bug Bugs related to dependencies or plugins
Projects
None yet
Development

No branches or pull requests

3 participants