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

Maybe it should be fiber instead of fibers in package.json #16

Closed
tai271828 opened this issue Dec 4, 2021 · 3 comments
Closed

Maybe it should be fiber instead of fibers in package.json #16

tai271828 opened this issue Dec 4, 2021 · 3 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@tai271828
Copy link

Describe the bug
Missing fiber files when executing npm run serve .

To Reproduce

  1. Step up this project from scratch by following README.md
  2. npm run serve

Expected behavior
npm setups successfully and shows message like Done Compiled successfully

Additional context
Workaround: npm unstall fibers, npm install fiber, and then npm run serve

@tai271828 tai271828 added the bug Something isn't working label Dec 4, 2021
@tai271828
Copy link
Author

The fix has been fixed. Anyone is more than welcome to verify the fix and update your verification here to help others!

@tai271828 tai271828 added this to the alpha milestone Jan 23, 2022
@tai271828 tai271828 modified the milestones: alpha, beta Feb 23, 2022
@tai271828
Copy link
Author

Ah, upstream disfactory fixed the issue and bumps to node 16! Disfactory#151

It's pity that we forgot to upstream the fix : (

@tai271828
Copy link
Author

@yanghaochang104 FYI, if you are re-setting up your development laptop, this issue may happy to you.

If you can resolve the issue by the same approach, pull requests are more than welcome : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants