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 for
Just a heads up: JS module scripts (
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
m
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
runtime
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 lis
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 a
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
This
7 matches
Mail list logo