project - Standard CoffeeScript output layout -
is there de facto standard filesystem output layout of compiled coffeescript output?
or: should .js
, .map
files end up?
i have file watcher1 compiling output ./grounds/[whatever]
keep source folder clean, end like:
index.html /js ├──foo.js ├──bar.js /coffee ├──a.coffee ├──b.coffee ├──/grounds │ ├──a.js │ ├──a.map │ ├──b.js │ ├──b.map ├──/some-module │ ├──c.coffee │ ├──/grounds │ │ ├──c.js │ │ ├──c.map
just curious if missed boat on existing standard output file layout, or if folks let them siblings in same folder , happy that.
1: pycharm
i don't think standard, development, use same structure js coffee:
eg:
coffee ├── advancedstatsmodule.coffee ├── board │ ├── board.coffee │ ├── card.coffee ├── controllers │ ├── directives.coffee │ ├── factory.coffee │ ├── filters.coffee │ ├── listcontroller.coffee public/js ├── advancedstatsmodule.js ├── board │ ├── board.js │ ├── card.js ├── controllers │ ├── directives.js │ ├── factory.js │ ├── filters.js │ ├── listcontroller.js
advantages this:
- js , coffee not mixed
- the coffee directory not public
for production, concat , minify files anyway.
update:
i use gulp that. gulpfile:
var watch= require('gulp-watch'); var coffee= require('gulp-coffee'); gulp.src(paths.coffee) .pipe(watch(function(files) { return files.pipe(coffee()) .pipe(gulp.dest(paths.js)); }));
Comments
Post a Comment