Re:Malicious crossenv package on npm
by TrickyRick on Wednesday August 02, 2017 @07:34AM
(#14909686)
Seems like they went completely overboard in terms of complexity. Why not have any camel/kebab/snake case reserve the same word in any type of casing? I.e. if I submit cross-env I also get crossenv, cross_env and crossEnv for free. Same goes if I submit any of the others (Exception of course being "crossenv" which only reserves "crossenv").
[ Parent
| on HN ]
There are no comments on this comment yet.