fix(adapter-netlify)!: write output conforming to Netlify Frameworks API#15294
Draft
serhalp wants to merge 20 commits intosveltejs:mainfrom
Draft
fix(adapter-netlify)!: write output conforming to Netlify Frameworks API#15294serhalp wants to merge 20 commits intosveltejs:mainfrom
serhalp wants to merge 20 commits intosveltejs:mainfrom
Conversation
The Netlify adapter now generates "v2" Netlify Functions, which uses modern standards (ESM, Request, Response) instead of the legacy "Lambda-compatible" or "v1" format. Under the hood, this greatly simplifies the adapter code and improves maintainability. See more details in this guide: https://developers.netlify.com/guides/migrating-to-the-modern-netlify-functions/. Some key changes: - The use of Request/Resonse eliminated the need for special header parsing, special multi-value handling header, base64 encoding of binary responses, and more. - Configuration of function routing directly in code eliminated the need for `_redirects` file generation. - As a bonus, this removes the limitation that users cannot specify redirects in `netlify.toml`. BREAKING CHANGES: - `platform.context` type changed to https://docs.netlify.com/build/functions/api/#netlify-specific-context-object
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
This reverts commit 0d14399.
🦋 Changeset detectedLatest commit: e29d240 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
serhalp
changed the title
serhalp
commented
Feb 10, 2026
| builder.instrument?.({ | ||
| entrypoint: `.netlify/functions-internal/${FUNCTION_PREFIX}render.mjs`, | ||
| instrumentation: '.netlify/server/instrumentation.server.js', | ||
| start: `.netlify/functions-start/${FUNCTION_PREFIX}render.start.mjs`, |
Contributor
Author
There was a problem hiding this comment.
TODO: I have no idea what this was yet
teemingc
reviewed
Feb 12, 2026
teemingc
reviewed
Feb 12, 2026
Co-authored-by: Tee Ming <chewteeming01@gmail.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
(Stacked on top of #15203)closes #15169
The current implementation of the Netlify adapter writes output to paths and config files that are under-documented and in some cases entirely undocumented.
18 months ago, Netlify addressed this by releasing the stable, documented Netlify Frameworks API](https://docs.netlify.com/build/frameworks/frameworks-api/).
This PR migrates the adapter to write output that conforms to this spec.
POTENTIALLY BREAKING CHANGE: Deploying and previewing with Netlify CLI now requires v17.31.0 or later. Run
npm i -g netlify-cli@latestto upgrade.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm testand lint the project withpnpm lintandpnpm checkChangesets
pnpm changesetand following the prompts. Changesets that add features should beminorand those that fix bugs should bepatch. Please prefix changeset messages withfeat:,fix:, orchore:.Edits