I have no problem writing some preprocessing packages with the standard method:
meteor create --package my:package
However when I look into some of the official/mature packages like coffeescript, the structure is very different. Say the package.js file is empty and all the same comment. They also have isopach.json, unipackage.json etc… Is there a tool or boilerplate for such structure?
I search the web for quite some time and didn’t find proper document or tutorial about this kind of package.
How should I proceed? Many thanks!