Intent to ship: Dynamic module imports (JS 'import()' syntax)

2019-03-07 Thread Jon Coppeard
I intend to enable dynamic module import on by default, to ship in Firefox 67. It has been developed behind the javascript.options.dynamicImport preference. This is already shipping in Chrome, Safari and Opera. Bug to turn on by default: https://bugzilla.mozilla.org/show_bug.cgi?id=1517546

Dynamic module imports are now enabled on nightly

2019-01-30 Thread Jon Coppeard
Hi, This is a heads-up that dynamic module imports have been enabled in nightly builds only for testing purposes. Dynamic import is described here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import#Dynamic_Imports Note that this feature works in both modules

Re: Intent to implement: Dynamic module imports (JS 'import()' syntax)

2018-10-22 Thread Jon Coppeard
On Saturday, 20 October 2018 09:54:05 UTC+1, David Baron wrote: > Have both Chrome and Safari shipped it without a secure context > restriction? Yes, it is supported outside of secure contexts in both Chrome and Safari. Jon ___ dev-platform mailing

Intent to implement: Dynamic module imports (JS 'import()' syntax)

2018-10-18 Thread Jon Coppeard
Summary: This introduces a function-like import() syntax to JS that imports an ES6 module and returns a promise for that module's namespace. We currently support static module imports and these should be used where possible. However sometimes it's desirable to dynamically load code at

Intent to implement and ship: import.meta in ES6 modules

2018-05-22 Thread Jon Coppeard
In an ES6 module, |import.meta| is new syntax that evaluates to an object that provides module-specific metadata from by the host environment. Currently only the 'url' property is provided, which is the base URL of the executing module. This allows modules to locate resources relative to the

JS modules are now enabled in nightly

2018-01-11 Thread Jon Coppeard
Just a heads up: JS module scripts

GC header file regoranisation

2017-11-16 Thread Jon Coppeard
In bug 1417123 I'm regorganising the GC header files a little. In summary: - if you need to use JS::Rooted, JS::Handle and the like please include js/RootingAPI.h. - if you need to configure the GC or trigger a collection please include js/GCAPI.h. The idea is to move everything required