-
-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Close #1506: PNPM monorepo with pnpm-lock.yaml
files.
#1514
Conversation
commit: |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is a critical CVE?Contains a Critical Common Vulnerability and Exposure (CVE). Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Take a deeper look at the dependencyTake 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 packageIf 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 riskTo ignore an alert, reply with a comment starting with
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ryoppippi Succeeded to restore pnpm-lock.yaml
, but bun
is not working on pnpm monorepo.
Oh yes. |
I'll work for removing Bun and fix rollup.config.js before v8.0 |
* Prepare `@samchon/openapi` v3 update (#1507) * Prepare next update of TypeScript (#1509) * No more `typia patch` command required (#1510) * Upgrade next version depepdency * Close #1506: PNPM monorepo with `pnpm-lock.yaml` files. (#1514) * Close #1506: PNPM monorepo with `pnpm-lock.yaml` files. * Update workflows * Fix build.yml * Fix build.yml again * Disable bun due to it does not support PNPM monorepo * feat: remvoe bun action (#1520) * Deprecate `llm.applicationOfValidate()` function. (#1524) * Publish v8.0 --------- Co-authored-by: ryoppippi <1560508+ryoppippi@users.noreply.github.com>
This pull request includes significant changes to the
typia
project, focusing on dependency updates, the switch from npm to pnpm for package management, and the removal of deprecated components. Below are the most important changes:Dependency Updates:
@types/body-parser
andfp-ts
tobenchmark/package.json
. [1] [2]body-parser
to version1.20.3
inbenchmark/package.json
.Package Management:
npm
commands withpnpm
commands indeploy/index.ts
anddeploy/internal/DeployRunner.ts
. [1] [2] [3] [4]Removal of Deprecated Components:
ReplicaPublisher
and its associated logic fromdeploy/internal/DeployRunner.ts
anddeploy/internal/ReplicaPublisher.ts
. [1] [2]LICENSE
andREADME.md
files from thepackages/typescript-json
directory. [1] [2]Package Configuration:
version
and removed theprivate
field in the rootpackage.json
. [1] [2]typescript-json
package configuration frompackages/typescript-json/package.json
.These changes streamline the project by updating dependencies, improving package management, and removing deprecated components.