decap-cms: Breaking: `gatsby-plugin-netlify-cms` broken since #765.
gatsby-plugin-netlify-cms
seems to be broken on the CMS master since netlify/netlify-cms#765 was merged (i.e. >=1.2.0).
NOTE: A temporary fix is to revert to v1.1.0.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 24 (12 by maintainers)
@tech4him1 I understand it will convert everything. It only increased the 1.6M file by 40k, so I was curious why it was such a small increase. I am not sure we should do this as the solution, but it gives a place to start to figure out what the path we should take here π
Shawn released 1.2.0 today and it produced the error others are seeing. These confirm the errors I was getting on a master branch build using my test case above. I was able to get rid of the error by using a modified build of the CMS by removing the targets in the
presets
section of the.babelrc
My suspicion is that Gatsby is re-bundling the cms from our bundle and it is causing errors on that build. Here is a link to the Gatsby
.babel
presets export they usecc/ @tech4him1 , @erquhart
@tech4him1 In my project I still get my original error.
@tech4him1 For me
gatsby build
andyarn build
makes no difference β¦ and also my global gatsby-cli is up-to-date.@tech4him1 Yes; It was failing on current master, so testing against the
bitbucket-integration
does not matter unless master works.@pogo19 No problem. Hopefully we can figure out how to handle this.
To reproduce:
yarn remove netlify-cms
yarn add file:[path to local netlify-cms]
gatsby build
the starterI will confirm this as an issue again this morning.
Good point β Iβve been using
yarn link
so it stays linked (I checked thenode_modules
folder too π).@tech4him1 Will try tomorrow β¦ also please note that operations like
yarn add
oryarn install
rewrite your symlinked CMS to version from npm registry.For me the problem was present when trying to use netlify-cms (master branch build) in Gatsby using gatsby-plugin-netlify-cms Normally the problem isnβt present when CMS is used directly because browsers support βasyncβ keyword that appears in dist/cms.js (in current master HEAD).
@talves and @pogo19 were able to reproduce it, but I canβt. From Gitter (https://gitter.im/netlify/NetlifyCMS?at=5a7f00dfce68c3bc746c5972):