-
Notifications
You must be signed in to change notification settings - Fork 9
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: netlify/primitives
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: nuxt-v0.1.14
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: netlify/primitives
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: nuxt-v0.1.15
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 41 files changed
- 8 contributors
Commits on Aug 27, 2025
-
ci: allow triggering npm release with workflow_dispatch (#439)
* ci: allow triggering npm release with workflow_dispatch * chore: format
Configuration menu - View commit details
-
Copy full SHA for 7ed5b4b - Browse repository at this point
Copy the full SHA 7ed5b4bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 64b4fb4 - Browse repository at this point
Copy the full SHA 64b4fb4View commit details -
fix(dev): add support for
dev-server
context (#438)Related issue: netlify/cli#7585
Configuration menu - View commit details
-
Copy full SHA for 793b853 - Browse repository at this point
Copy the full SHA 793b853View commit details
Commits on Aug 28, 2025
-
fix: restore missing
Netlify
global type in@netlify/functions
(#434) * chore: fix existing vitest type tests These weren't asserting anything, and vitest type tests weren't enabled. * build: add missing `skipLibCheck` This is a tough one to explain. This was a latent issue due to a confluence of things: - we don't explicitly do type checking in this repo - instead we rely implicitly on the fact that we use tsup in part to build `.dts` files, which performs type checking - but tsup type checking behaves slightly differently than just running `tsc` in various little ways, largely because it's scoped per entrypoint - we weren't setting `skipLibCheck: true` in the `tsconfig.json`, which seemed reasonable as there were no errors inside `node_modules/` - now when I went to set up vitest type tests, this started type checking some stuff under the hood, and this failed with type errors inside `node_modules/`, despite it using our `tsconfig.json` - it turns out this is because the tsup type checking approach was not encountering these errors; you can confirm this by running `npx --package=typescript tsc --noEmit` in `packages/functions/` So, TL;DR: we had a latent necessity for `skipLibCheck` obscured by our weird implicit type checking via `tsup --dts`. --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: serhalp <[email protected]> Co-authored-by: Philippe Serhal <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 2e028b9 - Browse repository at this point
Copy the full SHA 2e028b9View commit details -
fix(vite-plugin): pass environmentVariables option to NetlifyDev (#442)
* fix(vite-plugin): pass environmentVariables option to NetlifyDev
Configuration menu - View commit details
-
Copy full SHA for 214ac26 - Browse repository at this point
Copy the full SHA 214ac26View commit details
Commits on Aug 29, 2025
-
Co-authored-by: token-generator-app[bot] <82042599+token-generator-app[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 2f2beb4 - Browse repository at this point
Copy the full SHA 2f2beb4View 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 nuxt-v0.1.14...nuxt-v0.1.15