-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
wzrd.in but as a scoped npm registry instead of a cdn #102
Comments
Wonderful idea 👍 As an alternative naming: Also for reference: sindresorhus/ama#446 |
@ewnd9 the proposed naming you suggest wouldn't work unless you made the registry completely a mirror, and that would require all package installs to go through that mirror (at least the metadata, not sure about the protocol if the tgz can come from a different server), which would force the maintainer of this service to have higher bandwidth needs. putting everything under a scope allows only the transpiled packages to be fetched from the es5 transpiler registry (which is what |
I've actually told CDNJS that this is the only way they're going to stay relevant moving forward (see cdnjs/cdnjs#8531 (comment)) |
Except ES6 is supported and the official ECMAScript way to handle modules. You are expected as a module developer to either compile or distribute browser-ready code if you want any of your modules to be use on the Web "moving forward" |
I think it might be best to create an NPM org and upload browserified bundles there. |
A service like https://github.com/browserify/wzrd.in (browserify as a service), but instead of browserifying, uses babel to transpile it to es5 (or an option of environment with babel-preset-env). So, a package like whatwg-url would be installed via
and scope names would remove the
@
and replace the/
with--
(like@angular/cli
->angular--cli
, which i think is unused enough. or make the custom registry support some character that is allowed to be installed by the cli but not by the official registry (uppercase? starting with an underscore?)Inspired by the issue seen at jsdom/whatwg-url#105
The text was updated successfully, but these errors were encountered: