gatsby build and not during the dev build
If you do not write any state logic or event handlers then this should not effect you. This feature may be something this plugin wants to
tackle in the future.
How to install
gatsby-config.js as it relies on onPreRenderHTML
⚠️Make sure you enter a string 'a-string' instead of JS regexp like
/a-string/, Gatsby has trouble handing off regular expressions to plugins. The string you pass in will be handled as a regular expression for you.
- An array of paths that are to be excluded from removing all the JS. The code runs a "contains" so this can be used to block a directory and all subdirectories, or to get as specific as you want.
When do I use this plugin?
Examples of usage
Upgrade Guide v1 -> v2
- Update the
excludeFilesin your gatsby-config file. The value passed in is exactly the same as it was before.
How to run tests
npm run test
We also test against the minimum supported Node version of Gatsby up to the latest version during each pull request to make sure the code will work for all supported NodeJS versions. You can find this configuration in the Cloud Build config file.
How to develop locally
This project relies on Typescript for all the type safety goodness which can be found in the
src directory. The compiled output goes
directly into the root of the project because Gatsby expects certain files
to be in the root.
- Get the latest updates
npm run watchto tell Typescript to listen to changes in the
srcdirectory and recompile on the fly.
- Link this package to an actual gatsby project to test the plugin working, there is a good article for this here.
How to contribute
See the contributing docs
Code of conduct
See the code of conduct