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

Publishing untranspiled version #401

Open
Sharlaan opened this issue Nov 14, 2017 · 0 comments
Open

Publishing untranspiled version #401

Sharlaan opened this issue Nov 14, 2017 · 0 comments

Comments

@Sharlaan
Copy link

Sharlaan commented Nov 14, 2017

Currently, NWB auto-publishes via Travis (with a simple update of package.json version will trigger the npm publish) into 2 folders:
es/ contains transpiled code except native import/export
lib/ contains fully transpiled code

Suggestion :

Would it be possible to publish 2 versions:

  • one fully transpiled (es5) in lib/
  • one non-transpiled (native es8) in es/

then in README, explain :

in your site, use this:

<script type="module" src="es/index.js"></script>
<script nomodule src="lib/index.js"></script>

This is based on asumption that historically, if a browser supports type="module", then will have near 100% support of ES7, fetch API, Promises, and Async/Await, without polyfilling or transpiling.

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

1 participant