Jiwon Choi

Hey everyone, sorry for letting this slip. Feel free to ping me if [15.0.1-canary.2](https://github.com/vercel/next.js/releases/tag/v15.0.1-canary.2) did not fix it. When we can confirm, will have the patch ASAP to unblock your...

@Sayakie Thank you! @faisalrehmanlums Could you add the `next info` as well? I wasn't able to reproduce this issue on my VM, which I think it slipped. 

@faisalrehmanlums Hi, https://github.com/vercel/next.js/pull/71673 hasn't been added to the release yet, ~~expected to be at `15.0.1-canary.4`~~. Could you try `v15.0.2-canary.0`? Thank you!

@dualdetail @Rakvadium @faisalrehmanlums Since I cannot reproduce the case, it isn't easy to fix it confidently. Could you confirm the `npx [email protected]` does not work? https://github.com/user-attachments/assets/ab93e716-f51a-4c3b-a2db-dabbdc6457e0 ``` Operating System: Platform:...

@dualdetail Could you try removing `node_modules/` (the root one as well) & `.next/`?

Could you guys all try the `15.0.2-canary.10`? Hope this is our final fix. Kudos to @elitalpa for the PR!

Hey everyone, v15.0.2 is out with the fix. Please give it a try and lmk!

Thank you for the PR @martinsione! Your implementation is correct, I just moved it to the internal `` tag of Shadow DOM and added a test. Thank you again!

* **#71693** 👈 * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @devjiwonchoi and the rest of your teammates on Graphite

@eric-burel I'm currently improving the design of `requiredEnv`, would love to hear more about your use case. Current `requiredEnv` check runs on the **loaded envs** during the build (initial part...