errors encountered in parcel 2 beta.1 #4762
Unanswered
bugzpodder
asked this question in
General
Replies: 2 comments 9 replies
-
The issue with versioning is unfortunately just how npm and yarn work... The issue with the watcher has a solution in an open PR: parcel-bundler/watcher#34 It should probably detect @mischnic any idea why react-fast-refresh fails? |
Beta Was this translation helpful? Give feedback.
2 replies
-
There is no error message in that snippet.
That is technically a warning but it should still not happen. Using a babel.config.json in a monorepo works fine for me. Can you share a reproduction? |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Ran into a variety of issues when testing out parcel2-beta.1
Installed some parcel packages, it defaulted to [email protected] rather than @next/beta.1, causing some weird errors when trying start parcel. Adding @next tag and reinstalling solved it.
@parcel/config-default @parcel/runtime-react-refresh @parcel/transformer-react-refresh-babel @parcel/transformer-react-refresh-wrap @parcel/validator-typescript
I disabled build scripts (b/c of yarn 2) and got a non-descriptive error for @parcel/watch
enabled build scripts and it worked fine.
I added a .parcelrc (to get @parcel/transformer-raw)
Got a good build but it says Page not found:
and I removed .parcelrc removed .parcelrc, but parcel just read from cache and didn't rebuild from scratch based on new config file. had to rm -rf .parcel_cache (would appreciate some CLI command)
I had a babel.config.js and got an error for react-refresh:
removing babel.config.js worked.
got this error, couldn't find a workaround
yarn: 2.0.0-rc.33
node: v10.20.1
macos 10.15.5
Beta Was this translation helpful? Give feedback.
All reactions