Skip to content
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

Node 20 not supporting prepack script (Module Author) #278

Open
leopradac opened this issue May 27, 2024 · 6 comments
Open

Node 20 not supporting prepack script (Module Author) #278

leopradac opened this issue May 27, 2024 · 6 comments

Comments

@leopradac
Copy link

Environment

  • Operating System: Darwin
  • Node Version: v20.11.0
  • Nuxt Version: 3.11.2
  • CLI Version: 3.11.1
  • Nitro Version: 2.9.6
  • Package Manager: npm@10.2.4
  • Builder: -
  • User Config: -
  • Runtime Modules: -
  • Build Modules: -

Reproduction

I will use npm as a sample, feel free to replicate it with yarn, pnpm, or bun.

Following the Module Author Guide:

npx nuxi init -t module my-module
once it is finished

npm run dev:prepare
npm run prepack

It will retrieve

ℹ Building my-module
ℹ Cleaning dist directory: ./dist

And that's it, it gets stuck there.

It happens to me while

  • using nuxt, @nuxt-kit, @nuxt-schema at "3.11.2"
  • node 20

Those facing the same issue so far the only workaround for me was switching to node18.

Describe the bug

prepack script (module build) gets stuck while cleaning dist directory

Additional context

Already been tested in MacOS and Ubuntu.
Also tried two Node20 versions: v20.13.1 and v20.11.0.
Switched to Node v18.20.3 with the exact same project and works perfectly fine.

Logs

ℹ Building my-module
ℹ Cleaning dist directory: ./dist
Copy link

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

@danielroe danielroe transferred this issue from nuxt/nuxt May 29, 2024
@arashsheyda
Copy link
Member

I'm experiencing the same issue, here is a fresh project on stackblitz for reproduction

@userquin
Copy link
Member

userquin commented Jun 3, 2024

try adding nuxt-module-build prepare && to the prepack script:
"prepack": "nuxt-module-build prepare && nuxt-module-build build",

@arashsheyda
Copy link
Member

@userquin thanks! solved my problem

@userquin
Copy link
Member

userquin commented Jun 3, 2024

I'm going to file an issue in the starter template and send the corresponding PR.

@danielroe
Copy link
Member

danielroe commented Jun 4, 2024

Is someone experiencing an issue even after running dev:prepare? And if so do you have the updated tsconfig.json here and the updated dev:prepare script?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants