Replies: 2 comments
-
Need more information about the issue. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I've converted this to a discussion. Can change it back to a bug report if it turns out it's a bug in node itself and not in, for example, a module that gets loaded. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Version
16.14.2
Platform
No response
Subsystem
npm
What steps will reproduce the bug?
when i run npm run dev this error show i'm using next js framework for this
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
No response
What do you see instead?
Additional information
how to fix this segmentation fault in npm
Beta Was this translation helpful? Give feedback.
All reactions