npm WARN deprecated uglifyjs@2.4.11: uglifyjs is deprecated - use uglify-js instead.
npm WARN engine request@2.79.0: wanted: {"node":">= 4"} (current: {"node":"0.12.18","npm":"2.15.11"})
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN engine esprima@4.0.0: wanted: {"node":">=4"} (current: {"node":"0.12.18","npm":"2.15.11"})
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN engine hash-base@3.0.4: wanted: {"node":">=4"} (current: {"node":"0.12.18","npm":"2.15.11"})
npm WARN engine hash-base@3.0.4: wanted: {"node":">=4"} (current: {"node":"0.12.18","npm":"2.15.11"})
npm WARN engine hash-base@3.0.4: wanted: {"node":">=4"} (current: {"node":"0.12.18","npm":"2.15.11"})
these can easily be fixed in the build process, is there a particular reason the dependencies haven't been updated?
Additionally, why is make being use instead of npm scripts? it seems a bit odd and breaks compatibility for windows...
these can easily be fixed in the build process, is there a particular reason the dependencies haven't been updated?
Additionally, why is
makebeing use instead of npm scripts? it seems a bit odd and breaks compatibility for windows...