Closed xzilja closed 6 years ago
@IljaDaderko can you narrow this down to a single package update? e.g. roll back to your old versions and then update them one by one until you see the error. The error looks like it's originating from gatsby-plugin-jss
so maybe start with that plugin?
@m-allanson on it 👍
After some fiddling issue was unrelated to package updates it was conflict between jss and styled-components gatsby plugins where I needed to remove styled components plugin and re-add it in gatsby-ssr
@IljaDaderko could you post what you did in gatsby-ssr
I think I'm running into the same issue. I'm not entirely sure if it's styled-components
that is causing the issue though. Thanks!
@rockchalkwushock unfortunately I no longer have access to the project where I implemented the fix :/ from the top of my head issue was due to gatsby plugins I used particularly
gatsby-plugin-jsx used together with gatsby-styled-components
I ended up removing styled components one and applying it in gatsby-ssr
through default styled components ssr using ServerStyleSheet, StyleSheetManager
as per https://www.styled-components.com/docs/advanced#server-side-rendering
I see thanks for your quick response.
Description
I updated some gatsby dependencies today and started getting production build errors, there are some links which I visited, but none seem to explain issue in detail nor does the error specify any of my files (it refers mainly to react-dom and gatsby). I have also not made any changes since yestrday besides package update, it was building fine before.
Steps to reproduce
These were my packages from before
That were updated to these versions today
Expected result
Should build fine as before.
Actual result
I received this error during HTML build phase
Environment
File contents (if changed):
gatsby-config.js
:package.json
:gatsby-node.js
: not changedgatsby-browser.js
: not changedgatsby-ssr.js
: not changed