fix(docs): add netlify init configuration steps for Netlify
#1929
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
✅ Deploy Preview for analog-app ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for analog-blog ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for analog-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Using the Netlify CLI automatically configures the build settings, so this commit documents this as the preferred configuration approach.
|
Thanks @serhalp! We would definitely like to make it zero config if possible. I thought there was some auto-detection set up for Analog at some point. We'll likely revisit the output directory when nitro v3 goes stable. |
brandonroberts
approved these changes
Nov 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
PR Checklist
The Netlify deployment docs currently only document a manual configuration approach using the Netlify app's UI.
What is the new behavior?
Using the Netlify CLI instead automatically configures the build settings, so this PR documents this as the preferred configuration approach, documents the
netlify.tomlthat this generates, and moves the manual UI-based configuration to a "Manual configuration" subsection.Does this PR introduce a breaking change?
Other information
This is out of scope for this PR but... FYI we'd love to be able to not need that manual functions dir step. Our current framework auto-configuration system doesn't support populating this field. We've never needed this for any other framework, because our assumption is that frameworks will respect the Netlify Frameworks API when targeting Netlify. Since you're using Nitro (which does this in its Netlify presets), I'm curious why this is ending up in
dist/analog? 🤔[optional] What gif best describes this PR or how it makes you feel?