ehmicky

A plugin author (@brunoquaresma) [have asked](https://community.netlify.com/t/building-plugin-secret-inputs/14550) for the possibility to add secret inputs. At the moment, Build plugins can do this using either: - environment variables - the filesystem (reading...

Move `npm install` and `yarn` logic from the buildbot to Netlify Build

3

Build plugins [are installed](https://github.com/netlify/build/blob/b9f414b808b993abd9590d44fbfea87d03eb6bf3/packages/build/src/install/main.js#L77) using `npm install` or `yarn`. We already install dependencies using [`npm install`](https://github.com/netlify/build-image/blob/3a3e63f876b1fa8702f47ede08f4e691d1ba5fbe/run-build-functions.sh#L125) or [`yarn`](https://github.com/netlify/build-image/blob/3a3e63f876b1fa8702f47ede08f4e691d1ba5fbe/run-build-functions.sh#L73) in the buildbot. The buildbot logic includes several features: caching, `YARN_VERSION`, `NPM_VERSION`,...

This issue is part of the bigger issue at #40. Also related to #667. Some environment variables are used mainly inside the buildbot's internal logic. Most (but not all) are...

Two Yarn-related tests are currently always failing on my local machine (and randomly in CI). We should first skip those. https://github.com/netlify/build/blob/e49f7dccd218d942429d39b48bbedc6a7bc83356/packages/build/tests/install/tests.js#L106-L115 Then, https://github.com/netlify/pod-workflow/issues/215 will remove the need for those tests...

## Problem `@netlify/config` validates configuration properties. For example, the following is valid: ```toml [context.production] command = "test" ``` But the following is invalid (`context` should not be a string) and...

## Test error in Example.com **ExampleException** in **home#example** Something really bad happened [View on Bugsnag](http://app.bugsnag.com/errors/example/events/example?i=gh&m=te) ## Stacktrace app/controllers/home_controller.rb:123 - example app/controllers/other_controller.rb:12 - broken lib/important/magic.rb:4 - load_something [View full stacktrace](http://app.bugsnag.com/errors/example/events/example?i=gh&m=te) *Created...

Improve how the list of Functions is printed in the build logs

4

Background and initial discussions at https://github.com/netlify/build/pull/2018 When Functions are being bundled in a build, we currently print them like this:  Those are the Functions source files. The following information...

Two Yarn-related tests are failing on Node `

Users can enable the following core plugin in their `netlify.toml`: ```toml [[plugins]] package = "@netlify/plugin-local-install-core" ``` When enabled, `npm install` or `yarn` is run inside each local plugin's directory. More...

This is due to a bug in AVA. I've reported it here: https://github.com/avajs/ava/issues/2311