@babel/preset-react and babel-plugin-dynamic-import-node

[KatSick]

is there any reason why @babel/preset-react and babel-plugin-dynamic-import-node in dependencies section of the package.json and not in devDependencies?

It bloats our application node_modules a lot, because of it

[ljharb]

Because they're runtime dependencies:

• happo.io/src/createWebpackBundle.js

  Line 34 in c4eb30a

  plugins: [require.resolve('babel-plugin-dynamic-import-node')],

• happo.io/src/createWebpackBundle.js

  Line 5 in c4eb30a

  const babelPresetReact = require.resolve('@babel/preset-react');

[KatSick]

@ljharb I agree, but for example here

happo.io/src/createWebpackBundle.js

Line 10 in c4eb30a

return require('webpack');

you are using webpack but do not specify it in dependencies

I'm asking, because we are using Happo with Cypress, without any babel configurations, and I'm wondering how can I avoid it.

as I understand, as soon as this is not a monorepo with more modular packages which can be published separately it is not possible?

--
thanks for super fast reponse!

[ljharb]

https://github.com/happo/happo.io/blob/master/package.json#L109 is where webpack is specified as a peer dep.

I don't think you can avoid it.

[KatSick]

@ljharb can we move babel presets to peerDeps as well? (sorry for all the questions)

[ljharb]

Peer deps are strictly required, so that wouldn't help your problem at all - it'd just be a breaking change and additional burden on users to install them themselves.