Warn when running `deploy` without build if using build plugin that modifies config
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- cli
Research direction
Start by tracing the netlify build and netlify deploy flows when a build plugin mutates configuration, using the linked Next.js plugin issue as context. Determine whether normalized configuration can be persisted safely; otherwise, done means netlify deploy warns when a prior build changed configuration and suggests netlify deploy --build.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Currently, if a use runs netlify build and then netlify deploy, any config changes made by a build plugin are lost because they are not persisted. This can be confusing. e.g. https://github.com/netlify/netlify-plugin-nextjs/issues/953
Describe the solution you'd like
The ideal would be if the config were persisted, so if build had been run then it would save the normalised config in .netlify, and if the other config was unchanged then it would deploy that instead. However if that isn't possible it would be good to add a warning if deploying after a build in which the config has been mutated, suggesting that the user run netlify deploy --build instead.
Describe alternatives you've considered
Add the same check in the build plugin itself.
Can you submit a pull request?
I can do this is if we think it's a good approach
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 474
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 53
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from netlify/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area: command: deploy area: docs type: feature
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
type: feature
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
type: bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·