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

NPM Install Fails with Code EBADPLATFORM #37

Open
DevDimov opened this issue Jun 26, 2024 · 4 comments
Open

NPM Install Fails with Code EBADPLATFORM #37

DevDimov opened this issue Jun 26, 2024 · 4 comments

Comments

@DevDimov
Copy link

When I cloned the repository and ran npm i, I got an error about an npm package called fsevents which does not support my operating system (Windows). Any ideas how to resolve this? Possibly replace with a cross-platform alternative like Chokidar?

npm warn old lockfile
npm warn old lockfile The package-lock.json file was created with an old version of npm,
npm warn old lockfile so supplemental metadata must be fetched from the registry.
npm warn old lockfile
npm warn old lockfile This is a one-time fix-up, please be patient...
npm warn old lockfile
npm error code EBADPLATFORM
npm error notsup Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin"} (current: {"os":"win32"})
npm error notsup Valid os:  darwin
npm error notsup Actual os: win32

Screenshot 2024-06-26 084152

@sam3d
Copy link

sam3d commented Jun 26, 2024

The npm install didn't actually fail :) It sure looks like it does, but it's safe to ignore this error

https://www.npmjs.com/package/fsevents#troubleshooting

I'm getting EBADPLATFORM Unsupported platform for fsevents error.
It's fine, nothing is broken. fsevents is macos-only. Other platforms are skipped. If you want to hide this warning, report a bug to NPM bugtracker asking them to hide ebadplatform warnings by default.

@DevDimov
Copy link
Author

Hey @sam3d, a node_modules folder is not being created unfortunately.

@sam3d
Copy link

sam3d commented Jun 26, 2024

Please could you provide the complete installation log output?

@DevDimov
Copy link
Author

Sure, here it is.
2024-06-27T14_31_24_562Z-debug-0.log

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

No branches or pull requests

2 participants