Thank you for reporting this.

addyo@: Are you the right person to handle this?

Workbox isn't part of Chrome so I am guessing this bug should be closed, but I don't know where to replicate this report without making it public.

Thanks for pointing this out.

We were planning on publishing the workbox-navigation-preload package to npm for the first time with the upcoming 3.4.0 release of Workbox. We use lerna (https://github.com/lerna/lerna) to publish all dependencies at once, though now that the workbox-navigation-preload package name has been claimed by someone else, the act of publishing to npm will fail, and we'll have to choose a different package name.

Given that we need to check in code to the master branch of GitHub prior to publishing to npm via lerna, I'm not sure how to avoid a gap in time between when there's a reference to an upcoming project in the GitHub codebase and the time at which we actually go live on npm. Perhaps this would force our hand to move to scoped namespaces in the future: https://docs.npmjs.com/misc/scope

https://github.com/GoogleChrome/workbox/pull/1570 will remove the reference to workbox-navigation-preload in the master branch of the GitHub repo, once it's merged.

We never published anything that references workbox-navigation-preload to npm, so there's nothing to remediate there.

In the short term, we could start squatting on our future npm project names (including whichever new name we choose for the Navigation Preload module) with an empty 0.0.1 release prior to committing anything to GitHub.

And then there's https://docs.npmjs.com/misc/scope as a cleaner way of avoiding this.

Heya, no problem.

If it can help, I can transfer the ownership of the package name to you.

Preben

Thanks Jeffrey. Since there is no longer any immediate user risk I will close this, and suggest moving further discussion to a Github issue.

(https://github.com/GoogleChrome/workbox/pull/1570 is merged, and there's currently no active reference to workbox-navigation-preload in the master branch of the GitHub repo.)

Thanks for offering to do the transfer, Preben! I would appreciate it just to avoid confusion, though it's not clear whether we'll actually go ahead with that package name.

My npm account name is jeffposnick.

We (the Workbox team) will take responsibility for following one of the options outlined in #4 for preventing a recurrence when the project adds more npm packages.

Sure, just transferred the ownership: https://www.npmjs.com/package/workbox-navigation-preload.

Thanks
Preben

Looks good—thanks again, Preben!

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot