Value of `netlifyConfig.build.processing` passed to plugins does not reflect values set in the UI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 258
- Forks
- 108
- Avg merge
- 1d
- Merged PRs (30d)
- 22
Description
Describe the bug
If a site has enabled post-processing in the UI, this fact is not exposed in the config object passed top plugins. This is in contrast to other build settings which do include UI values. It would be useful to have acess to this, because frameworks may need to warn a user if it is incompatible with their settings. See https://github.com/netlify/netlify-plugin-nextjs/issues/994
Configuration
- Enable post-processing on a site
- Log value of
netlifyConfig.build.processinginonPreBuild - Observe it is always set to
{ css: {}, html: {}, images: {}, js: {} }
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.
Research direction
Start by reproducing the configuration in a build plugin's onPreBuild hook: enable post-processing in the site UI and log netlifyConfig.build.processing. Trace where UI build settings are assembled into the plugin config, then verify that the logged processing values reflect the enabled settings rather than empty objects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100