-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
@parcel/core: The plugin "@parcel/packager-svg" is not compatible with the current version of Parcel. #6854
Comments
So the way I "fixed" it temporarily locally is I just edited |
Looks like #6911 |
Yes, indeed! Works in the latest nightly with that commit. |
Same problem has surfaced again now after the 2.0.0 release;
|
Make sure you updated all of the plugins you have installed and verified that your lock file isn't causing older versions to stay installed |
I get the same error using both
(I had to edit package.json between pnpm and yarn to change the deploy script to work with |
You still have some older nightly versions in your project |
I just went through and added all parcel packages to package.json using "nightly", then nuked all yarn files and did a reinstall, and both before and after doing that, this is the contents of
|
"devDependencies": {
"@parcel/babel-ast-utils": "nightly",
"@parcel/babylon-walk": "nightly",
"@parcel/bundler-default": "nightly",
"@parcel/cache": "nightly",
"@parcel/codeframe": "nightly",
"@parcel/config-default": "nightly",
"@parcel/core": "nightly",
"@parcel/diagnostic": "nightly",
"@parcel/events": "nightly",
"@parcel/fs-search": "nightly",
"@parcel/fs-write-stream-atomic": "nightly",
"@parcel/fs": "nightly",
"@parcel/graph": "nightly",
"@parcel/hash": "nightly",
"@parcel/logger": "nightly",
"@parcel/markdown-ansi": "nightly",
"@parcel/namer-default": "nightly",
"@parcel/node-libs-browser": "nightly",
"@parcel/node-resolver-core": "nightly",
"@parcel/optimizer-cssnano": "nightly",
"@parcel/optimizer-htmlnano": "nightly",
"@parcel/optimizer-terser": "nightly",
"@parcel/package-manager": "nightly",
"@parcel/packager-css": "nightly",
"@parcel/packager-html": "nightly",
"@parcel/packager-js": "nightly",
"@parcel/packager-raw-url": "nightly",
"@parcel/packager-raw": "nightly",
"@parcel/plugin": "nightly",
"@parcel/reporter-cli": "nightly",
"@parcel/reporter-dev-server": "nightly",
"@parcel/resolver-default": "nightly",
"@parcel/runtime-browser": "nightly",
"@parcel/runtime-js": "nightly",
"@parcel/runtime-react-refresh": "nightly",
"@parcel/source-map": "nightly",
"@parcel/transformer-babel": "nightly",
"@parcel/transformer-css": "nightly",
"@parcel/transformer-html": "nightly",
"@parcel/transformer-image": "nightly",
"@parcel/transformer-js": "nightly",
"@parcel/transformer-json": "nightly",
"@parcel/transformer-postcss": "nightly",
"@parcel/transformer-posthtml": "nightly",
"@parcel/transformer-raw": "nightly",
"@parcel/transformer-react-refresh-wrap": "nightly",
"@parcel/transformer-react-refresh": "nightly",
"@parcel/transformer-sass": "nightly",
"@parcel/transformer-svg": "nightly",
"@parcel/transformer-webmanifest": "nightly",
"@parcel/types": "nightly",
"@parcel/utils": "nightly",
"@parcel/watcher": "nightly",
"@parcel/workers": "nightly",
"parcel": "nightly",
"sass": "latest"
} |
π bug report
Build fails, look below for output and possible solution π
package.json
π€ Expected Behavior
Should build as normal.
I've tried this with nuking node_modules and related files/locks/etc with npm 7.20+, yarn 3.0.0 and pnpm 6.14.x+ using both
npm run
andpnpm run
.π― Current Behavior
(same result with earlier and later nightlies)
π Possible Solution
Depend on ">=2.0.0-nightly" instead of "^2.0.0-rc.0" maybe? I'm not sure what is better, these semver ranges don't really concern me - all my projects use "latest" or "nightly" or whatever and when a problem crops up I just solve it and apply the fix to every project immediately.
(I picked 5.4.1 because it's what is used here https://github.com/parcel-bundler/parcel/blob/v2/packages/transformers/js/package.json#L43 but it's the same result with the most recent release of https://github.com/npm/node-semver; 7.3.5)
See #6828 (comment)
Thank you!
The text was updated successfully, but these errors were encountered: