Commit 2a41584

authored

docs(configuration): add example for managedPaths (#6604)

* docs(configuration): add example for managedPaths * update

1 parent 314beb2 commit 2a41584Copy full SHA for 2a41584

File tree

+17

-1

lines changed

+17

-1

lines changed

Lines changed: 17 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -444,7 +444,23 @@ Make sure to wrap the path in a capture group if you use regular expressions.`
`444`	`444`
`445`	`445`	`An array of paths that are managed by a package manager and can be trusted to not be modified otherwise.`
`446`	`446`
`447`		`-Make sure to wrap the path in a capture group if you use regular expressions.`
	`447`	+Make sure you wrap the path in a capture group if you are using regular expressions so webpack can extract the path, for example, here's a RegExp webpack internally uses to match the `node_modules` directory:
	`448`	`+`
	`449`	+```text
	`450`	`+/^(.+?[\\/]node_modules)[\\/]/`
	`451`	+```
	`452`	`+`
	`453`	+A common use case for `managedPaths` would be to exclude some folders from `node_modules`, e.g. you want webpack to know that files in the `node_modules/@azure/msal-browser` folder are expected to change, which can be done with a regular expression like the one below:
	`454`	`+`
	`455`	+```js
	`456`	`+module.exports = {`
	`457`	`+ snapshot: {`
	`458`	`+ managedPaths: [`
	`459`	`+ /^(.+?[\\/]node_modules[\\/](?!(@azure[\\/]msal-browser))(@.+?[\\/])?.+?)[\\/]/,`
	`460`	`+ ],`
	`461`	`+ },`
	`462`	`+};`
	`463`	+```
`448`	`464`
`449`	`465`	`### module`
`450`	`466`

Comments

(0)