From 2717f8f515edfb958e556a1af62a419aeaa353fd Mon Sep 17 00:00:00 2001 From: Lukas Taegert-Atkinson Date: Tue, 1 Mar 2022 14:32:14 +0100 Subject: [PATCH] Deprecate namespaceToStringTag in favour of generatedCode.symbols --- docs/999-big-list-of-options.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/999-big-list-of-options.md b/docs/999-big-list-of-options.md index 5b2dfb04d66..a7c75661137 100755 --- a/docs/999-big-list-of-options.md +++ b/docs/999-big-list-of-options.md @@ -593,7 +593,10 @@ const foo = 42; exports.foo = foo; // cjs output with symbols: true -Object.defineProperties(exports, { __esModule: { value: true }, [Symbol.toStringTag]: { value: 'Module' } }); +Object.defineProperties(exports, { + __esModule: { value: true }, + [Symbol.toStringTag]: { value: 'Module' } +}); const foo = 42; @@ -1901,8 +1904,7 @@ You can also supply a list of external ids to be considered pure or a function t #### output.namespaceToStringTag -_Use [`output.generatedCode.symbols`](guide/en/#outputgeneratedcode) instead._
-Type: `boolean`
CLI: `--namespaceToStringTag`/`--no-namespaceToStringTag`
Default: `false` +_Use [`output.generatedCode.symbols`](guide/en/#outputgeneratedcode) instead._
Type: `boolean`
CLI: `--namespaceToStringTag`/`--no-namespaceToStringTag`
Default: `false` Whether to add spec compliant `.toString()` tags to namespace objects. If this option is set,