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

Failed to install latest google-closure-deps@20191027.0.1 #996

Closed
teppeis opened this issue Nov 12, 2019 · 3 comments
Closed

Failed to install latest google-closure-deps@20191027.0.1 #996

teppeis opened this issue Nov 12, 2019 · 3 comments
Labels
internal-issue-created An internal Google tracking issue has been created triage-done Initial triage has been completed for this issue

Comments

@teppeis
Copy link
Contributor

teppeis commented Nov 12, 2019

The latest google-closure-deps@20191027.0.1 requires google-closure-compiler@^v20191027.0.1, but it's missing.

$ npm i google-closure-deps
npm ERR! code ETARGET
npm ERR! notarget No matching version found for google-closure-compiler@^v20191027.0.1.
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 'google-closure-deps'
npm ERR! notarget

https://www.npmjs.com/package/google-closure-compiler?activeTab=versions
@teppeis teppeis mentioned this issue Nov 12, 2019
Closed
@mprobst
Copy link

mprobst commented Nov 12, 2019

Internal issue created: b/144351395

@mprobst mprobst added internal-issue-created An internal Google tracking issue has been created triage-done Initial triage has been completed for this issue labels Nov 12, 2019
@teppeis
Copy link
Contributor Author

teppeis commented Dec 10, 2019

Because v20191111 was released, this issue doesn't occur in the latest.
npm i google-closure-deps@ 20191027 reproduces it.

@shicks
Copy link
Member

shicks commented Dec 14, 2019

That release had an abnormality, and apparently I didn't fix it correctly. Given that 20191111 seems to have fixed it, and it was a one-off issue, I think we should close this as obsolete.

@shicks shicks closed this as completed Dec 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
internal-issue-created An internal Google tracking issue has been created triage-done Initial triage has been completed for this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mprobst @teppeis @shicks