samchon / tgrid

TypeScript RPC (Remote Procedure Call) for WebSocket and Worker protocols
https://tgrid.com/
MIT License
141 stars 19 forks source link

Uniform error pattern. #85

Closed samchon closed 3 months ago

samchon commented 3 months ago

No more use tstl's Error extended custom error classes, but just utilize pure Error class. Also, normalized every error messages to start from the Error on Class.method(): message... prefix.

Also, AcceptorBase.inspectReady() had wrong conditional statement about closing event. This PR also fixes it.

socket-security[bot] commented 3 months ago

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

Package New capabilities Transitives Size Publisher
npm/@mui/icons-material@5.15.20 None +2 19 MB brijeshb42
npm/@mui/material@5.15.20 environment +31 22 MB brijeshb42
npm/@rollup/browser@4.18.0 eval, network +1 5.61 MB lukastaegert
npm/@rollup/plugin-terser@0.4.4 eval, unsafe Transitive: environment +5 2.35 MB lukastaegert
npm/@rollup/plugin-typescript@11.1.6 environment, filesystem +2 242 kB shellscape
npm/@types/browserify@12.0.40 None +1 21.2 kB types
npm/@types/node@18.19.39 None +1 2.04 MB types
npm/@types/puppeteer@7.0.4 None 0 1.76 kB types
npm/@types/react@18.3.3 None +2 1.69 MB types
npm/@typescript-eslint/eslint-plugin@5.62.0 Transitive: environment, filesystem +23 6.84 MB jameshenry
npm/@typescript-eslint/parser@5.62.0 Transitive: environment, filesystem +11 2 MB jameshenry
npm/browserify@17.0.0 filesystem, network, unsafe Transitive: environment, eval +95 4.87 MB goto-bus-stop
npm/eslint@8.57.0 environment, filesystem Transitive: eval, unsafe +48 9.04 MB eslintbot
npm/local-web-server@2.6.1 Transitive: environment, filesystem, network, shell, unsafe +34 864 kB 75lb
npm/mv@2.1.1 filesystem 0 10.3 kB superjoe
npm/next@14.2.4 environment, filesystem, network, shell, unsafe +23 1.2 GB vercel-release-bot
npm/puppeteer@22.12.0 environment 0 334 kB google-wombot
npm/rimraf@5.0.7 environment, filesystem Transitive: shell +35 3.63 MB isaacs
npm/rollup@4.18.0 environment, filesystem 0 2.28 MB lukastaegert
npm/ts-patch@3.2.0 environment, filesystem +2 402 kB nonara
npm/typedoc@0.26.2 Transitive: environment, filesystem +12 4.95 MB typedoc-bot
npm/typescript-transform-paths@3.4.7 filesystem 0 142 kB danielpanpm
npm/whatwg-fetch@3.6.20 network 0 57.4 kB jakechampion
npm/ws@7.5.10 network 0 122 kB lpinca

🚮 Removed packages: npm/@mui/icons-material@5.15.16, npm/@mui/material@5.15.16, npm/@rollup/browser@4.17.2, npm/@types/node@18.19.31, npm/@types/prettier@3.0.0, npm/@types/react@18.3.1, npm/lz-string@1.5.0, npm/monaco-editor@0.39.0, npm/next@14.1.1, npm/path@0.12.7, npm/prettier@3.2.5, npm/rimraf@5.0.5, npm/tgrid@0.10.3, npm/ts-loader@9.5.1, npm/typedoc@0.25.13, npm/typia@6.0.3, npm/webpack-cli@5.1.4, npm/webpack@5.91.0, npm/write-file-webpack-plugin@4.5.1

View full report↗︎

socket-security[bot] commented 3 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/puppeteer@22.12.0 🚫

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/puppeteer@22.12.0