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

No binaries are currently downloaded #44

Open
maxrandolph opened this issue Aug 19, 2021 · 11 comments
Open

No binaries are currently downloaded #44

maxrandolph opened this issue Aug 19, 2021 · 11 comments

Comments

@maxrandolph
Copy link

npm install chromium seems to be broken currently. The file structure after running the install command leaves the node_modules/chromium folder without any binaries:

image

@maxrandolph
Copy link
Author

Seems that https://www.googleapis.com/storage/v1/b/chromium-browser-snapshots/o/Mac%2F913272%2Fchrome-mac.zip?alt=media is returning a 404 so it's possibly on Google's side.

@theoutlander
Copy link

theoutlander commented Aug 19, 2021

Here's a link that works (instead of 913272 it needs refs_heads_main-913272):

https://www.googleapis.com/storage/v1/b/chromium-browser-snapshots/o/Mac%2Frefs_heads_main-913272%2Fchrome-mac.zip?alt=media

@maxrandolph
Copy link
Author

maxrandolph commented Aug 19, 2021

From above link, a workaround can be specifying the revision number in .npmrc:

node_chromium_revision=refs_heads_main-913272

edit: this seems to fail on windows still but works for osx and linux

@theoutlander
Copy link

Not sure if this is a temporary issue, but the last well known version following the numeric pattern is:

https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/913132/

@theoutlander
Copy link

theoutlander commented Aug 19, 2021

I suspect Google posted an incorrect value in the LAST CHANGE file. Maybe this might get resolved in a day?

image

@maxrandolph
Copy link
Author

Opened a quick and dirty fix for this: #45

@maxrandolph
Copy link
Author

PR should resolve issue on all OS

@dtolstyi
Copy link
Owner

Hi @maxrandolph, thank you for all the info, investigation and PR. I've just checked 'win' folders and revision specified in LAST_CHANGE file seems to be present as usual without any prefixes.
I would still prefer to wait a bit with applying PR to be sure that system did really change and that this is not just one-time case.
I can see that instructions at official chromium website are still the same and they don't say anything about the prefixes.

@maxrandolph
Copy link
Author

Sounds good @dtolstyi. Thanks for the reply and for looking into it. It's possibly just a temporary glitch on Google's storage api which may fix itself with time. Noticed that yesterday the issue seemed to go away for a couple hours but then the LAST_CHANGE revision version for mac and windows was having issues while the other OS flavors were not.

@maxrandolph
Copy link
Author

Also thanks for providing the useful utility :-)

@ChesterCorin
Copy link

@maxrandolph issue seems to have been resolved, for now.
terminal
folder

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

4 participants