Npm devDependencies get added on package builds


#1

I noticed after Meteor 1.3 the npm devDependencies on my project get loaded as part of my package significantly increasing the time it takes to do the meteor publish and updates. Is that normal or would that be considered a bug?

I’m developing an angular1 directive so it does not have the ES6 module capability of angular2 at the moment.


#2

Found a way around it. For anything with devDependencies which is usually from my ‘gulpfile.js’ I just use an alias for require

var r = require
var gulp = r('gulp')

I had noted it here as well http://www.trajano.net/2016/04/using-gulp-with-meteor/?preview=1&_ppp=1d78837d7a