-
Notifications
You must be signed in to change notification settings - Fork 14
Issue with nextjs 8 #76
Comments
I get this error:
|
Not sure what causes the error as the style tag in component.js looks fine, but a downgrade to |
it seems that styled-jsx is pinned in yarn.lock to 3.1.0 |
I'm checking this, since I only use it on personal projects I'm doing it only when I have time. |
@sergiodxa it looks like |
adding to package.json "resolutions": {
"styled-jsx": "3.2.1"
}, did not fix it but adding "resolutions": {
"styled-jsx": "3.0.0"
}, solved it for me. |
Same for me, works with "3.0.0" but not with the latest "3.2.1" |
Hmm, this is rather curious, once I apply the lock file from: #84 this issue is fixed, but there are quite a few packages. Even when on the main repository(master branch on next-nprogress) if I rebuild the package the issue seems settled. |
@sergiodxa Thank you for this package! Since downgrading |
I don't have time to check this, if someone wants to send a PR I could merge it and publish a new version with the merged code. |
OK thank you! Here is an alternative: https://github.com/zeit/next.js/tree/canary/examples/with-loading |
In case anyone is having issues with this, here's a solution that worked for me (extending the example in the link posted by @rap2hpoutre above) Install and import nprogress
Copy the css file from here and save it to your project (paste it in your existing base css file or create a new one and import it in your entry file) Paste the following code in your root (entry) file. Here, I am using
ExplanationA
By clearing the timeout, |
Our you just copy the component into your project (with source attribution of course :) ). |
That issue still persists, what I did to avoid this was to do this in the
|
Hello, I'm not maintaining this anymore because I'm not using it anymore in my projects and I don't have time to work on it. Feel free to fork and publish to npm with another name. |
Since upgrading to nextjs 8 I'm getting an issue with styled-jsx
The text was updated successfully, but these errors were encountered: