-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: pnpm/pnpm
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v8.15.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: pnpm/pnpm
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v8.15.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 17 commits
- 120 files changed
- 3 contributors
Commits on Jan 30, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 44062ee - Browse repository at this point
Copy the full SHA 44062eeView commit details
Commits on Jan 31, 2024
-
chore(pd): make esbuild find
js-yaml
correctly (#7598)* chore(pd): make esbuild find `js-yaml` correctly For some reason, esbuild uses the upstream version of `js-yaml` rather than the @zkochan fork. This throws a little plugin into esbuild's resolution to resolve `js-yaml` using Node's resolvers instead, which seems to find the correct version. There may be a better way to do this, especially considering esbuild does fine in the normal build of pnpm as far as I can tell... though that may be because `tsc` does the first pass.
Configuration menu - View commit details
-
Copy full SHA for d7a6cbf - Browse repository at this point
Copy the full SHA d7a6cbfView commit details -
Configuration menu - View commit details
-
Copy full SHA for 211d2ac - Browse repository at this point
Copy the full SHA 211d2acView commit details
Commits on Feb 3, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 7b0d5c2 - Browse repository at this point
Copy the full SHA 7b0d5c2View commit details
Commits on Feb 6, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 85e96dc - Browse repository at this point
Copy the full SHA 85e96dcView commit details
Commits on Feb 8, 2024
-
Configuration menu - View commit details
-
Copy full SHA for ab193d6 - Browse repository at this point
Copy the full SHA ab193d6View commit details -
chore(pd): ensure pd always runs with sourcemaps (#7628)
This change makes it so that `pd` starts a Node process and passes `--enable-source-maps` to it, which allows for better debugging when `pd` commands fail. I'm not sure if this will work on Windows since it changes a simple `require` to a `childProcess.execSync`.
Configuration menu - View commit details
-
Copy full SHA for e979676 - Browse repository at this point
Copy the full SHA e979676View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5dff47f - Browse repository at this point
Copy the full SHA 5dff47fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 738d443 - Browse repository at this point
Copy the full SHA 738d443View commit details -
Configuration menu - View commit details
-
Copy full SHA for dc48925 - Browse repository at this point
Copy the full SHA dc48925View commit details
Commits on Feb 12, 2024
-
Configuration menu - View commit details
-
Copy full SHA for abf3909 - Browse repository at this point
Copy the full SHA abf3909View commit details -
fix(get-context): avoid excess purge prompts (#7639)
* fix(get-context): avoid excess purge prompts pnpm sometimes needs to purge modules folders (node_modules) when certain configuration changes (in other words, when it needs to start from scratch). This prompt, problematically, was getting triggered asynchronously for each importer in the workspace that needed a purge, which would sometimes lead to gargantuan prompts instead of one consolidated prompt. The fix is to queue up which importers need a purge, then fire the prompter all at once. Closes #7320 * fix: reuse ImporterToPurge type * refactor: apply suggestions from code review --------- Co-authored-by: Zoltan Kochan <z@kochan.io>
Configuration menu - View commit details
-
Copy full SHA for ceb47e3 - Browse repository at this point
Copy the full SHA ceb47e3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 58c9031 - Browse repository at this point
Copy the full SHA 58c9031View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6df9b66 - Browse repository at this point
Copy the full SHA 6df9b66View commit details -
Configuration menu - View commit details
-
Copy full SHA for fbe6714 - Browse repository at this point
Copy the full SHA fbe6714View commit details -
Configuration menu - View commit details
-
Copy full SHA for 822b2da - Browse repository at this point
Copy the full SHA 822b2daView commit details -
Configuration menu - View commit details
-
Copy full SHA for a2e7250 - Browse repository at this point
Copy the full SHA a2e7250View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v8.15.1...v8.15.2