lavamoat/webpack setup

[naugtur]

Policy generation works with no quirks to pave over with overrides.
Project successfully builds.
lockdown inlining solved with html-webpack-plugin itself. There's room for improvement, but it's pretty simple as is.
I did not remove the pre-existing browserify build.

Using typescript for weback config is not ideal, because it's a common problem that depending on how your dependencies arrange/dedupe you may get type mismatches between your webpack version and plugins. This problem will start manifesting itself once we publish types for the plugin. As soon as the version of webpack we take types from differs from the version used in the repo, we're risking a mismatch of the webpack plugin type (even for minor changes)

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@discoveryjs/json-ext@0.5.7	None	0	81.1 kB	lahmatiy
npm/@endo/env-options@1.1.2	None	0	28.1 kB	kriskowal
npm/@lavamoat/webpack@0.3.0-beta.0	eval	0	67.5 kB	boneskull
npm/@polka/url@1.0.0-next.23	None	0	4.38 kB	lukeed
npm/@types/webpack-bundle-analyzer@4.6.3	None	0	9.15 kB	types
npm/gzip-size@6.0.0	filesystem	0	7.93 kB	sindresorhus
npm/lavamoat@8.0.6	eval	+2	89.3 kB	boneskull
npm/mrmime@1.0.1	None	0	31 kB	lukeed
npm/opener@1.5.2	shell	0	6.21 kB	domenic
npm/ses@1.4.0	None	0	3.32 MB	kriskowal
npm/sirv@2.0.3	filesystem	0	20.7 kB	lukeed
npm/totalist@3.0.1	filesystem	0	7.46 kB	lukeed
npm/tsconfig-paths-webpack-plugin@4.1.0	Transitive: environment, filesystem, unsafe	+1	490 kB	jonaskello
npm/webpack-bundle-analyzer@4.10.1	environment, filesystem, network Transitive: shell	+3	1.51 MB	valscion

🚮 Removed packages: npm/@discoveryjs/json-ext@0.5.6, npm/@endo/env-options@1.1.0, npm/lavamoat@8.0.4, npm/ses@1.1.0, npm/tsconfig-paths-webpack-plugin@4.0.1

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/opener@1.5.2, npm/webpack-bundle-analyzer@4.10.1

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[naugtur]

@SocketSecurity ignore npm/webpack-bundle-analyzer@4.10.1 - uses http for local server
@SocketSecurity ignore npm/opener@1.5.2 - the whole purpose of the package is running child processes