-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
TypeError: Cannot read properties of null (reading 'render') #5480
Comments
A smaller version in repl |
I'm working on a PR, will be finished soon |
This issue has been resolved via #5481 as part of rollup@4.16.1. You can test it via |
Fixed: elchininet/shadow-dom-selector#56 Thanks for the quick fix 👍🏼 |
I get a similar error when running a build with Vite
The problem seems to be in
Could you please suggest if this something not covered yet in rollup, or a misconfiguration on my side? |
It is most probably a rollup error, I will check it later. |
@mshabarov Could you please provide a minimal way to reproduce? |
@liuly0322 not a minimal example project, unfortunately, but I'm able to reproduce with the example project that is attached to this issue- "k8s-demo-app.zip". Download the project and run |
Yes, it is a rollup bug, thanks for spotting. It's weird that I don't know how to solve it now and will have a detailed look later. some logs:
It seems that there should be a new |
The above issue has been fixed for us in |
This issue has been resolved via #5483 as part of rollup@4.17.0. You can test it via |
1 similar comment
This issue has been resolved via #5483 as part of rollup@4.17.0. You can test it via |
Rollup Version
4.16.0
Operating System (or Browser)
Ubuntu 20.04.6 LTS / MacOS Sonoma 14.4.1
Node Version (if applicable)
18.20.2
Link To Reproduction
elchininet/shadow-dom-selector#55
Expected Behaviour
Build should success as it succeeded on previous versions.
Actual Behaviour
Build fails with an error coming from
ConditionalExpression.render
:I tried to reproduce it in Repl without success, but seeing that it is coming from
ConditionalExpression.render
that was recently refactored this could give a clue to the devs.The text was updated successfully, but these errors were encountered: