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
{{ message }}
Repository navigation
--experimental modules flags should have warnings #30600
Currently the following experimental modules flags don't have warnings:
--experimental-json-modules
--experimental-wasm-modules
--experimental-resolve-self
--experimental-conditional-exports
--es-module-specifier-resolution=node
Ideally when using any of these flags we should provide a warning message that not only is the base experimental modules implementation unstable, but these flags are not even clear if they will be provided as final features in the implementation and any of them might be removed still.
For at least --experimental-json-modules, --experimental-wasm-modules it should be possible to move the warnings to their first use.
For --experimental-resolve-self and --experimental-conditional-exports the first use would be within C++ code and applies both to the CJS and ESM resolver implementations so may be a bit trickier, but it is in theory possible.
Activity
pd4d10 commentedon Nov 23, 2019
If multiple experimental flags specified, should these warnings emitted separately for every flag, or merged into one?
guybedford commentedon Nov 23, 2019
I would prefer one for each. Warning consolidation is a separate consideration for Node.js more generally I think.
guybedford commentedon Nov 23, 2019
For at least
--experimental-json-modules,--experimental-wasm-modulesit should be possible to move the warnings to their first use.For
--experimental-resolve-selfand--experimental-conditional-exportsthe first use would be within C++ code and applies both to the CJS and ESM resolver implementations so may be a bit trickier, but it is in theory possible.module: add warnings for experimental flags
module: add warnings for experimental flags
module: add warnings for experimental flags