Can't compile "using" keyword

[hazae41]

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/shy-sound-kgyv86?file=%2Fapp%2Flayout.tsx%3A1%2C14

To Reproduce

Write some code with the using keyword

e.g.

class Disposer {
  [Symbol.dispose]() {
    console.log("Disposed")
  }
}

export default function Page({ children }) {
  useEffect(() => {
    using disposer = new Disposer()
  }, [])
  
  return null
}

Current vs. Expected behavior

> build
> next build

   ▲ Next.js 15.0.4-canary.5

   Creating an optimized production build ...
Failed to compile.

./app/layout.tsx
Module not found: Can't resolve '@swc/helpers/_/_ts_add_disposable_resource'

https://nextjs.org/docs/messages/module-not-found

./app/layout.tsx
Module not found: Can't resolve '@swc/helpers/_/_ts_dispose_resources'

https://nextjs.org/docs/messages/module-not-found


> Build failed because of webpack errors

Provide environment information

Next.js 15.0.4-canary.5

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

Output (export/standalone), SWC, Webpack

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

next build (local)

Additional context

It works in 15.0.2, but not in 15.0.3 nor 15.0.4

[aidenlx]

additional report: next dev that use babel reports the same error in v15.0.4, and next dev --turbopack does not even transplie the syntax even with explicit_resource_management: true enabled in swc

PS: the official name for using keyword is ECMAScript Explicit Resource Management. may worth mentioning in description.

[aidenlx]

seems like 15.0.3-canary.8 breaks the transpile. It may be related to swc_core update to v5.0.1

[aidenlx]

may related: swc-project/swc#9673

[aidenlx]

confirmed that it's fixed in 15.0.4-canary.49

next dev --turbopack does not even transplie the syntax even with explicit_resource_management: true enabled in swc)

It's still not fixed. I've opened a separate issue around turbopack dev server with using keyword in #73739

[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.