i18next / react-i18next

Internationalization for react done right. Using the i18next i18n ecosystem.
https://react.i18next.com
MIT License
9.23k stars 1.02k forks source link

Build config and optimizations #1769

Closed VIKTORVAV99 closed 2 months ago

VIKTORVAV99 commented 2 months ago

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

adrai commented 2 months ago

still failing :-(

socket-security[bot] commented 2 months ago

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

Package New capabilities Transitives Size Publisher
npm/babel-preset-razzle@4.0.5 environment +16 571 kB razzle-bot
npm/express@4.17.1 environment, filesystem, network Transitive: eval +41 1.18 MB dougwilson
npm/html-webpack-plugin@5.3.1 filesystem, unsafe Transitive: environment, network, shell +28 2 MB jantimon
npm/i18next-browser-languagedetector@6.1.2 None 0 76.4 kB adrai
npm/i18next-fs-backend@1.1.1 eval, filesystem 0 485 kB adrai
npm/i18next-http-backend@1.2.8 network +2 309 kB adrai
npm/i18next-http-middleware@3.1.4 environment 0 103 kB adrai
npm/i18next@20.3.5 None 0 504 kB jamuhl
npm/mini-css-extract-plugin@1.4.1 unsafe Transitive: environment, eval +8 1.39 MB evilebottnawi
npm/razzle-dev-utils@4.0.5 Transitive: environment, filesystem, network, shell, unsafe +141 6.5 MB razzle-bot
npm/razzle@4.0.5 Transitive: environment, eval, filesystem, network, shell, unsafe +587 42.8 MB razzle-bot
npm/react-dom@17.0.2 environment +1 3.1 MB gaearon
npm/react-i18next@11.11.3 None 0 333 kB adrai
npm/react-router-dom@5.2.0 environment +8 1.56 MB mjackson
npm/react@17.0.2 environment 0 291 kB gaearon
npm/serve@11.3.2 Transitive: environment, eval, filesystem, network, shell +53 2.87 MB tootallnate

🚮 Removed packages: npm/i18next-browser-languagedetector@8.0.0, npm/i18next-http-backend@2.5.2, npm/i18next@23.11.5

View full report↗︎

socket-security[bot] commented 2 months ago

🚨 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 NoteSourceCI
Install scripts npm/fsevents@1.2.13
  • Install script: install
  • Source: node install.js
🚫

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/fsevents@1.2.13
coveralls commented 2 months ago

Coverage Status

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

adrai commented 2 months ago

still failing :-(

@VIKTORVAV99 https://github.com/i18next/react-i18next/pull/1773