disabled shadydom in node dev build#3526
Conversation
🦋 Changeset detectedLatest commit: 87754c1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Thank you for the PR! Ah.. this probably only happens when running in dev mode in Next.js and introduced with #3495. The tests you reference are passing because they are testing against the production Node build in which It makes no sense to keep that The lines here Lines 452 to 453 in feb2494 should also be added below here Line 496 in feb2494 |
|
excuse the delay, first day back in the office. i'll update the PR as suggested, and also generate a changeset |
58b998b to
af7ed29
Compare
|
ok, updated as per suggestion and dropped previous commit. re: changesets, should i just pick the |
I think a patch to Thank you! |
0738d57 to
2e5eae3
Compare
2e5eae3 to
0c433e3
Compare
|
added the changeset as recommended. i had to battle with the CLA check a little, but it's all good now. |
augustjk
left a comment
There was a problem hiding this comment.
Thank you very much!
I added a bit more description the changeset and tests for node dev builds.
|
Great, thanks! Appreciate you taking the time |
In a next.js environent this line was throwing because
windowis undefined. This module was imported transitively via a component importing the ref directive, which in turn imports async-directive, which in turn imports the file where the fix was added.Related #3156
I notice there are tests for
lit-htmlin that PR which import the ref directive, so i'm not sure how they pass (or conversely how it is not working for me)