-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
post-build.js should be moved into gatsby-node.js #239
Comments
This seems simple enough, I'd be happy to give this a go. Would you want to keep the existing |
Sorry this issue wasn't super clear. Right now if you add a Line 13 in 45ed32d
So the work to be done here is to move this API to Make sense? Thanks! |
This change allows the user to provide a babelrc or a babel section in their package.json. It also allows gatsby to be used without having to specifiy a babelrc if the user doesn't need anything past what babel provides as a default. * It resolves all of the paths to become absolute such that the user can crawl upwards as in gatsbyjs#239. * It allows the custom usage of other babel plugins so that decorators work as in gatsbyjs#129.
This change allows the user to provide a babelrc or a babel section in their package.json. It also allows gatsby to be used without having to specifiy a babelrc if the user doesn't need anything past what babel provides as a default. * It resolves all of the paths to become absolute such that the user can crawl upwards as in gatsbyjs#239. * It allows the custom usage of other babel plugins so that decorators work as in gatsbyjs#129.
Keep things simple. All node APIs in gatsby-node and all browser APIs in gatsby-browser.
The text was updated successfully, but these errors were encountered: