Worker not compiling correctly, window is undefined in files after canary 14.0.5-canary.19

[joacub]

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/trusting-glade-g3l38y?file=%2Fapp%2Fpage.tsx%3A7%2C1

To Reproduce

pnpm install
pnpm dev

show the console and see the window is undefined

Current vs. Expected behavior

window var is undefined and should be defined as this is in the browser context

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

after any canary 14.0.5-canary.19

Which area(s) are affected? (Select all that apply)

App Router, SWC transpilation

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

canary 14.0.5-canary.19 works perfectly

[joacub]

some one checking on this ? is being a blocker to update after .19 canary

[joacub]

plesaee some one can take care of this, this is a blocker. nextjs cant be used any more if you are using workers.

[joacub]

related:
#59603

[joacub]

@yf-yang you close something that still happening and is related to this

[kdy1]

Problematic release: https://github.com/vercel/next.js/releases/tag/v14.0.5-canary.20

[s0-david]

Doesn't seem to work on 14.1.1-canary.42 as well

[yf-yang]

Isn't it a correct behavior?
https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers#web_workers_api
If I got it right, in web worker, only self is available.

workers run in another global context that is different from the current window. Thus, using the window shortcut to get the current global scope (instead of self) within a Worker will return an error.

[joacub]

Isn't it a correct behavior? https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers#web_workers_api If I got it right, in web worker, only self is available.

workers run in another global context that is different from the current window. Thus, using the window shortcut to get the current global scope (instead of self) within a Worker will return an error.

not it is not, this was working before perfeclty

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.