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
This is a simple feature request (hence the lack of issue template). See this screenshot:
The Problem:
--production is dead-simple for humans to remember. --omit=dev, by contrast, is awful for humans. Every time I have to type the command I think, "What's that gobbledegook they changed '--production' to again? Eh, whatever, the old way works fine."
The Fix:
Just get rid of the CLI warning and let --production be an official alias for --omit=dev. The canonical build environments since the dawn of computers have been production and development, so it makes sense to recognize these as official aliases. For other, more nuanced environments, the --omit= parameter provides fine-grained control.
The text was updated successfully, but these errors were encountered:
Thank you for the suggestion, According to github guidelines, new feature and suggestions are discussed in the npm feedback forum. Recommended to open a discussion in the npm feedback forum. You can visit here https://github.com/npm/feedback/discussions
This is a simple feature request (hence the lack of issue template). See this screenshot:
The Problem:
--production
is dead-simple for humans to remember.--omit=dev
, by contrast, is awful for humans. Every time I have to type the command I think, "What's that gobbledegook they changed '--production' to again? Eh, whatever, the old way works fine."The Fix:
Just get rid of the CLI warning and let
--production
be an official alias for--omit=dev
. The canonical build environments since the dawn of computers have beenproduction
anddevelopment
, so it makes sense to recognize these as official aliases. For other, more nuanced environments, the--omit=
parameter provides fine-grained control.The text was updated successfully, but these errors were encountered: