Skip to content

[email protected] doesn't exist #5320

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

Closed
Erik-Stevens opened this issue Jan 25, 2019 · 4 comments
Closed

[email protected] doesn't exist #5320

Erik-Stevens opened this issue Jan 25, 2019 · 4 comments

Comments

@Erik-Stevens
Copy link

Issue Description

Project won't build because the parse-server package.json file contains dependency: [email protected], which does not exist. I believe the latest npm package for mongodb is 3.1.13.

npm ERR! notarget No matching version found for [email protected]
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'parse-server'

  • Server
    • parse-server version (Be specific! Don't say 'latest'.) : 3.1.3
    • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): Heroku

Logs

npm view mongodb versions --json
[
...
"2.2.36",
"3.0.0-rc0",
"3.0.0",
"3.0.1",
"3.0.2",
"3.0.3",
"3.0.4",
"3.0.5",
"3.0.6",
"3.0.7",
"3.0.8",
"3.0.9",
"3.0.10",
"3.0.11",
"3.1.0-beta1",
"3.1.0-beta2",
"3.1.0-beta3",
"3.1.0-beta4",
"3.1.0",
"3.1.1",
"3.1.2",
"3.1.3",
"3.1.4",
"3.1.5",
"3.1.6",
"3.1.7",
"3.1.8",
"3.1.9",
"3.1.10",
"3.1.11",
"3.1.12",
"3.1.13"
]

@flovilmart
Copy link
Contributor

It seems that npm unpublished 3.2.0 as the build was successful #5300

@dplewis
Copy link
Member

dplewis commented Jan 25, 2019

@flovilmart 3.2.0 was reverted mongodb/node-mongodb-native@508d685

Looks like they wanted to do a patch release instead of a minor release

@flovilmart
Copy link
Contributor

Well, it was published on npm at one point, and then unpublished :/

@flovilmart
Copy link
Contributor

The fix has been merged @Erik-Stevens . I don’t believe this was released in the wild, so next release will be OK

Sent with GitHawk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants