Deprecate namespaceToStringTag in favour of generatedCode.symbols

rollup · Mar 1, 2022 · e2c395b · e2c395b
1 parent c5fdd51
commit e2c395b
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 4 deletions.
diff --git 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._<br>
-Type: `boolean`<br> CLI: `--namespaceToStringTag`/`--no-namespaceToStringTag`<br> Default: `false`
+_Use [`output.generatedCode.symbols`](guide/en/#outputgeneratedcode) instead._<br> Type: `boolean`<br> CLI: `--namespaceToStringTag`/`--no-namespaceToStringTag`<br> Default: `false`
 
 Whether to add spec compliant `.toString()` tags to namespace objects. If this option is set,
 

diff --git a/test/form/samples/namespace-tostring/entry-named/_config.js b/test/form/samples/namespace-tostring/entry-named/_config.js
@@ -2,7 +2,7 @@ module.exports = {
 	description: 'adds Symbol.toStringTag property to entry chunks with named exports',
 	options: {
 		output: {
-			namespaceToStringTag: true,
+			generatedCode: { symbols: true },
 			exports: 'named',
 			name: 'bundle'
 		}