4 ms·
It's most likely due to backwards incompatibility. Major version update (1.x.x -> 2.0.0) breaks something and npm wants to play it safe, which is very understan
by bytearcher 11y ago
It's most likely due to backwards incompatibility. Major version update (1.x.x -> 2.0.0) breaks something and npm wants to play it safe, which is very understandable.