build
build copied to clipboard
Netlify Build (node process) runs the build command, Build Plugins and bundles Netlify Functions. Can be run in Buildbot or locally using Netlify CLI
When users are using old versions of Yarn (with the `YARN_VERSION` environment variable), the `--no-progress` CLI flag might not exist, making the build crash.
The current implementation of the plugin statuses does not allow users to know if a build failed due to a user error (e.g. wrong input), a plugin bug/crash, or a...
This is a request from @munter [here](https://github.com/Munter/netlify-plugin-hashfiles/issues/67#issuecomment-626400925). Also requested [here](https://github.com/cdeleeuwe/netlify-plugin-submit-sitemap/issues/4). > I'd say that categorises as a warning, not a build-breaking error. Btw is there any concept of being able...
Users can specify configuration properties for `netlify dev` using a `dev` section. ```toml [dev] functions = "my-functions" ``` Those configuration properties (used locally) are currently handled by Netlify CLI while...
At the moment, `utils.cache.list()` returns a promise resolving to an array with a list of files. When lots of files are being listed, this leads to builds hanging (see [this...
**Describe the bug** I'd like to write a plugin that caches a subdirectory of the home directory. It's unclear to me whether this is an intended but broken use case...
Error monitoring is currently only running in the production CI. CLI `netlify build` do not use it because they are lacking the Bugsnag API key. However some bugs might be...
It appears that `netlify-plugin-fetch-feeds` fails due to using a native module `node-expat` which shows a Node.js version mismatch error. [Example build logs](https://app.netlify.com/sites/mick/deploys/614b7f13be01d4384b7a67db#L225) What's strange is that this happens even when...
`@netlify/build` runs `yarn` on two instances, which are both opt-in behavior: - When the `@netlify/plugin-functions-install-core` plugin is used, we run `yarn` in the functions directory - When the `@netlify/plugin-local-install-core` plugin...
When the `--statsd.host` is provided, we should validate it is not an empty string. Context: we changed the value of that CLI flag and spent some time figuring out why...