Yes, I think that would be better. grunt
has their cli in a grunt-cli
, for instance.
Alternatively, you could leave that module name the same and change the one that's actually on the tessel. Personally, I think it's rather confusing that there's a magic thing you can require
only on the tessel, that isn't related to your node_modules
in the project you are deploying from. I think it would actually be less confusing to make that accessible through a global or do something like grunt:
module.exports = function(tessel) {
};
I know that globals are evil, but I feel that the magic around require('tessel')
is violating the principle of least surprise.