You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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:
then in README, explain :
in your site, use this:
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.The text was updated successfully, but these errors were encountered: