Duplicate plugin/preset detected. about complete-intro-to-react-v5 HOT 6 OPEN

Yes, I have encountered the same problem. This problem is coming from different node version. The proper solution is

1. uninstall this plugin with

npm uninstall @babel/plugin-proposal-class-properties

2. then disable it with commenting

{
  "presets": ["@babel/preset-react", "@babel/preset-env"],
  // "plugins": ["@babel/plugin-proposal-class-properties"]
}

3. clear the cache

npm run clear-build-cache

and then you are ready to run parcel again

from complete-intro-to-react-v5.

I'm also running into this issue.

Thanks, @Keromudo for posting your solution! Unfortunately, the solution above isn't working for me. I'm running into the following build error:

/Users/juno/Documents/fem/adopt-me/src/App.js: Cannot find module '@babel/preset-react, @babel/preset-env' from '/Users/juno/Documents/fem/adopt-me'

Interestingly, I get the same error regardless of whether the plugin is disabled in .bablerc. I've tried uninstalling all the dependencies and re-installing them, but this hasn't helped either.

I'm going to follow along the rest of the with class components, but if anyone knows of something to try, let me know! I'm curious about resolving this.

from complete-intro-to-react-v5.

Commenting the plugin breaks the code, doesn't it? @Keromudo

from complete-intro-to-react-v5.

@lizzSoup you may want to make sure you have these lines in your package.json:

"@babel/preset-env": "^7.12.7",    
"@babel/preset-react": "^7.12.7",

from complete-intro-to-react-v5.

Yes, I have encountered the same problem. This problem is coming from different node version. The proper solution is

1. uninstall this plugin with

npm uninstall @babel/plugin-proposal-class-properties

1. then disable it with commenting

{
  "presets": ["@babel/preset-react", "@babel/preset-env"],
  // "plugins": ["@babel/plugin-proposal-class-properties"]
}

1. clear the cache

npm run clear-build-cache

and then you are ready to run parcel again

Now clearing cache in npm is no possible

from complete-intro-to-react-v5.

For some reason the cache command didn't work for me, So instead I used npm cache clean --force

from complete-intro-to-react-v5.