You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since webpack produces an artifact that bundles all dependencies, none of the dependencies need to be available in the node environment at runtime (because there is no node environment in prod unless we are using node to serve the prod assets), so shouldn't we all be using devDependencies for everything? Is there any reason that we are not doing this or is it just a misleading convention?
The text was updated successfully, but these errors were encountered:
Since webpack produces an artifact that bundles all dependencies, none of the dependencies need to be available in the node environment at runtime (because there is no node environment in prod unless we are using node to serve the prod assets), so shouldn't we all be using devDependencies for everything? Is there any reason that we are not doing this or is it just a misleading convention?
The text was updated successfully, but these errors were encountered: