Hmmm. [email protected] is definitely published. I just tried the node upgrade and polymer-cli install myself and it was successful.
I wonder if there is something delayed on the npmjs CDN side. It wouldn't be the first time for that kind of thing. ~/s/s/cli-test λ nvm install 10 Downloading https://nodejs.org/dist/v10.15.2/node-v10.15.2-darwin-x64.tar.gz... ######################################################################## 100.0% Computing checksum with shasum -a 256 Checksums matched! Downloading and installing node v10.15.2... Now using node v10.15.2 (npm v6.4.1) ~/s/s/cli-test λ npm i -g polymer-cli /Users/brendanb/.nvm/versions/node/v10.15.2/bin/polymer -> /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/bin/polymer.js > [email protected] install /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/fsevents > node install node-pre-gyp WARN Using request for node-pre-gyp https download [fsevents] Success: "/Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" is installed via remote > [email protected] install /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/wd > node scripts/build-browser-scripts > [email protected] postinstall /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/spawn-sync > node postinstall > [email protected] postinstall /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/sauce-connect-launcher > node scripts/install.js || nodejs scripts/install.js > [email protected] postinstall /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/wct-sauce > node scripts/postinstall.js Prefetching the Sauce Connect binary. Missing Sauce Connect local proxy, downloading dependency This will only happen once. Downloading 10.0MB Archive checksum verified. Unzipping /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/sauce-connect-launcher/sc/sc-4.5.3-osx.zip Removing /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/sauce-connect-launcher/sc/sc-4.5.3-osx.zip Sauce Connect downloaded correctly > [email protected] postinstall /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/wct-local > node scripts/postinstall.js ---------- selenium-standalone installation starting ---------- --- selenium install: from: https://selenium-release.storage.googleapis.com/3.12/selenium-server-standalone-3.12.0.jar to: /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/selenium-standalone/.selenium/selenium-server/3.12.0-server.jar --- chrome install: from: https://chromedriver.storage.googleapis.com/2.43/chromedriver_mac64.zip to: /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/selenium-standalone/.selenium/chromedriver/2.43-x64-chromedriver --- firefox install: from: https://github.com/mozilla/geckodriver/releases/download/v0.23.0/geckodriver-v0.23.0-macos.tar.gz to: /Users/brendanb/.nvm/versions/node/v10.15.2/lib/node_modules/polymer-cli/node_modules/selenium-standalone/.selenium/geckodriver/0.23.0-x64-geckodriver ----- selenium-standalone installation finished ----- + [email protected] added 1295 packages from 1124 contributors in 28.233s On Mon, Mar 4, 2019 at 12:01 PM Thad Humphries <[email protected]> wrote: > The install for the Polymer CLI 1.9.7 appears to be broken. I just > upgraded Node.js from 10.15.1 to 10.15.2, and npm from 6.4.1 to 6.8.0. I > was told > > ╭────────────────────────────────────────╮ > │ │ > │ Update available 1.9.6 → 1.9.7 │ > │ Run npm i -g polymer-cli to update │ > │ │ > ╰────────────────────────────────────────╯ > > but got the following error: > > $ npm i -g polymer-cli > npm ERR! code ETARGET > 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 'polymer-cli' > npm ERR! notarget > > npm ERR! A complete log of this run can be found in: > npm ERR! /Users/thad/.npm/_logs/2019-03-04T16_18_14_852Z-debug.log > > I see the same error on two Macs, both running Mojave 10.14.3 > > Another user on the on the Slack channel sees the same problem: > https://polymer.slack.com/archives/C03PF4L4L/p1551727465278900 > > Follow Polymer on Google+: plus.google.com/107187849809354688692 > --- > You received this message because you are subscribed to the Google Groups > "Polymer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/polymer-dev/61c47e0b-18f6-4e17-8437-74288c1e7e38%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/61c47e0b-18f6-4e17-8437-74288c1e7e38%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAM4C%2B_YtTeUj1AY_DxJF5_6QNiVF-kfPsG2graWWFH%2BoXOmwQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
