@@ -110,17 +110,17 @@ export interface RollupCommonJSOptions {
110
110
* they should be left unconverted as it requires an optional dependency
111
111
* that may or may not be installed beside the rolled up package.
112
112
* Due to the conversion of `require` to a static `import` - the call is
113
- * hoisted to the top of the file, outside of the `try-catch` clause.
113
+ * hoisted to the top of the file, outside the `try-catch` clause.
114
114
*
115
- * - `true`: All `require` calls inside a `try` will be left unconverted.
115
+ * - `true`: Default. All `require` calls inside a `try` will be left unconverted.
116
116
* - `false`: All `require` calls inside a `try` will be converted as if the
117
117
* `try-catch` clause is not there.
118
118
* - `remove`: Remove all `require` calls from inside any `try` block.
119
119
* - `string[]`: Pass an array containing the IDs to left unconverted.
120
- * - `((id: string) => boolean|'remove')`: Pass a function that control
120
+ * - `((id: string) => boolean|'remove')`: Pass a function that controls
121
121
* individual IDs.
122
122
*
123
- * @default false
123
+ * @default true
124
124
*/
125
125
ignoreTryCatch ?:
126
126
| boolean
@@ -134,14 +134,14 @@ export interface RollupCommonJSOptions {
134
134
* NodeJS where ES modules can only import a default export from a CommonJS
135
135
* dependency.
136
136
*
137
- * If you set `esmExternals` to `true`, this plugins assumes that all
137
+ * If you set `esmExternals` to `true`, this plugin assumes that all
138
138
* external dependencies are ES modules and respect the
139
139
* `requireReturnsDefault` option. If that option is not set, they will be
140
140
* rendered as namespace imports.
141
141
*
142
142
* You can also supply an array of ids to be treated as ES modules, or a
143
- * function that will be passed each external id to determine if it is an ES
144
- * module.
143
+ * function that will be passed each external id to determine whether it is
144
+ * an ES module.
145
145
* @default false
146
146
*/
147
147
esmExternals ?: boolean | ReadonlyArray < string > | ( ( id : string ) => boolean )
@@ -159,7 +159,7 @@ export interface RollupCommonJSOptions {
159
159
* import * as foo from 'foo';
160
160
* ```
161
161
*
162
- * However there are some situations where this may not be desired.
162
+ * However, there are some situations where this may not be desired.
163
163
* For these situations, you can change Rollup's behaviour either globally or
164
164
* per module. To change it globally, set the `requireReturnsDefault` option
165
165
* to one of the following values:
@@ -210,7 +210,7 @@ export interface RollupCommonJSOptions {
210
210
* Some modules contain dynamic `require` calls, or require modules that
211
211
* contain circular dependencies, which are not handled well by static
212
212
* imports. Including those modules as `dynamicRequireTargets` will simulate a
213
- * CommonJS (NodeJS-like) environment for them with support for dynamic
213
+ * CommonJS (NodeJS-like) environment for them with support for dynamic
214
214
* dependencies. It also enables `strictRequires` for those modules.
215
215
*
216
216
* Note: In extreme cases, this feature may result in some paths being
@@ -224,7 +224,7 @@ export interface RollupCommonJSOptions {
224
224
* To avoid long paths when using the `dynamicRequireTargets` option, you can use this option to specify a directory
225
225
* that is a common parent for all files that use dynamic require statements. Using a directory higher up such as `/`
226
226
* may lead to unnecessarily long paths in the generated code and may expose directory names on your machine like your
227
- * home directory name. By default it uses the current working directory.
227
+ * home directory name. By default, it uses the current working directory.
228
228
*/
229
229
dynamicRequireRoot ?: string
230
230
}
0 commit comments