Right now, JSPM assumes chomp is globally installed as part of the prePublishOnly script. This is fragile because the chomp version is unspecified and so if there are incompatible versions of chomp, the build will break (or at
least results might be inconsistent.) By pinning chomp, we also make it explicitly part of the environment which will ensure running npm i; npm run prePublishOnly will work for new users.
Right now, JSPM assumes
chompis globally installed as part of theprePublishOnlyscript. This is fragile because thechompversion is unspecified and so if there are incompatible versions ofchomp, the build will break (or at least results might be inconsistent.) By pinningchomp, we also make it explicitly part of the environment which will ensure runningnpm i; npm run prePublishOnlywill work for new users.