Build config and optimizations

[VIKTORVAV99]

Changes the BABEL_ENV from jsnext to ESNext which should give the intended effects for es modules, this allows const functions to be used more without breaking the optimisations.

It also changes the targets and libs in tsconfig to match the minimum version needed for optional chaining to function (ES2020).

Checklist

• only relevant code is changed (make a diff before you submit the PR)
• run tests npm run test
• tests are included
• commit message and code follows the Developer's Certification of Origin

[adrai]

still failing :-(

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment	+16	571 kB	razzle-bot
npm/[email protected]	environment, filesystem, network Transitive: eval	+41	1.18 MB	dougwilson
npm/[email protected]	filesystem, unsafe Transitive: environment, network, shell	+28	2 MB	jantimon
npm/[email protected]	None	0	76.4 kB	adrai
npm/[email protected]	eval, filesystem	0	485 kB	adrai
npm/[email protected]	network	+2	309 kB	adrai
npm/[email protected]	environment	0	103 kB	adrai
npm/[email protected]	None	0	504 kB	jamuhl
npm/[email protected]	unsafe Transitive: environment, eval	+8	1.39 MB	evilebottnawi
npm/[email protected]	Transitive: environment, filesystem, network, shell, unsafe	+141	6.5 MB	razzle-bot
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+587	42.8 MB	razzle-bot
npm/[email protected]	environment	+1	3.1 MB	gaearon
npm/[email protected]	None	0	333 kB	adrai
npm/[email protected]	environment	+8	1.56 MB	mjackson
npm/[email protected]	environment	0	291 kB	gaearon
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell	+53	2.87 MB	tootallnate

🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Install scripts	npm/[email protected]	Install script: install Source: node install.js	example/razzle-ssr/package.json	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[coveralls]

coverage: 97.206% (-0.005%) from 97.211%
when pulling 6ecee8d on VIKTORVAV99:build_config_and_optimizations
into 34aa20d on i18next:master.

[adrai]

still failing :-(

@VIKTORVAV99 #1773