Skip to content

Commit 69445ce

Browse files
swyxioChristopherBiscardi
authored andcommitted
chore(docs): Remove "Transpiling Your Theme With Webpack" (#14106)
* Update converting-a-starter.md be consistent between yarn and npm * Update converting-a-starter.md This step is no longer required (as of very recently) Co-authored-by: Christopher Biscardi <[email protected]>
1 parent 2de2eff commit 69445ce

File tree

1 file changed

+0
-31
lines changed

1 file changed

+0
-31
lines changed

docs/docs/themes/converting-a-starter.md

Lines changed: 0 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -79,37 +79,6 @@ Then, tell the plugin to look in your theme's `src/pages` directory.
7979
},
8080
```
8181

82-
## Transpiling Your Theme With Webpack
83-
84-
**Note**: This is only needed temporarily. Themes will automatically be transpiled in later versions.
85-
86-
Since your theme will be installed, it will end up in `node_modules` which Gatsby doesn't transpile by default.
87-
This is something you can achieve with `gatsby-plugin-compile-es6-packages`.
88-
89-
You will need to install the package:
90-
91-
```shell
92-
yarn add gatsby-plugin-compile-es6-packages
93-
```
94-
95-
And then add it to your plugins list:
96-
97-
```js:title=gatsby-config.js
98-
const path = require("path")
99-
100-
module.exports = {
101-
plugins: [
102-
// ...
103-
{
104-
resolve: "gatsby-plugin-compile-es6-packages",
105-
options: {
106-
modules: ["gatsby-theme-NAME"],
107-
},
108-
},
109-
],
110-
}
111-
```
112-
11382
## Publishing to NPM
11483

11584
In order to allow others to install your theme you will need to publish it to npm. If you haven't published to npm before, learn how [here](https://docs.npmjs.com/packages-and-modules/contributing-packages-to-the-registry).

0 commit comments

Comments
 (0)