-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(internal): migrate to pnpm #8598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
33d1c19
to
a2b1ec8
Compare
8e4a7d2
to
8728bcb
Compare
ce8266b
to
60c6fab
Compare
60c6fab
to
39fcf02
Compare
39fcf02
to
7ada88e
Compare
7ada88e
to
4368b63
Compare
4368b63
to
d367ea5
Compare
d367ea5
to
7f40e47
Compare
7f40e47
to
dfe82a8
Compare
dfe82a8
to
0726fb5
Compare
0726fb5
to
a3c30ee
Compare
a3c30ee
to
c84bd37
Compare
fa2951a
to
3b92b76
Compare
c84bd37
to
bf9a1f9
Compare
bf9a1f9
to
044c447
Compare
044c447
to
e0cfde5
Compare
e0cfde5
to
1280e3a
Compare
1280e3a
to
e3c4380
Compare
setup pnpm in CI
e3c4380
to
47f26a0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrate package manager from Yarn to pnpm
This PR migrates the entire LangChain.js monorepo from Yarn to pnpm 10.14.0, providing improved performance, better disk space efficiency, and enhanced security.
🔄 Changes Made
Package Manager Configuration:
packageManager
field to[email protected]
(latest version)pnpm-workspace.yaml
to replace Yarn workspaces configurationresolutions
topnpm.overrides
format--filter
syntaxCI/CD Updates:
yarn
topnpm
pnpm install --frozen-lockfile
yarn workspace
topnpm --filter
Documentation Updates:
CONTRIBUTING.md
with pnpm instructionsREADME.md
to prioritize pnpm in installation instructionsWorkspace Dependencies:
@langchain/standard-tests
workspace dependency referencesworkspace:*
format for internal dependenciesCleanup:
.yarn/
directory (plugins, patches, releases)yarn.lock
filespnpm-lock.yaml
lockfile🚀 Benefits
node_modules
size through hard linking✅ Verification
pnpm install --frozen-lockfile
completes successfullypnpm --filter @langchain/core
)📋 Migration Notes
Developers will need to:
npm install -g pnpm
or use corepackpnpm install
instead ofyarn
pnpm --filter <package>
instead ofyarn workspace <package>
The migration is fully backward compatible in terms of functionality - all existing scripts and commands work the same way, just with pnpm instead of yarn.