-
Notifications
You must be signed in to change notification settings - Fork 129
Open
Description
Currently roots watch is failing silently. app.coffee is
records = require 'roots-records'
sass = require 'node-sass'
js_pipeline = require 'js-pipeline'
module.exports =
ignores: [
'**/_*/**/*', '**/_*', '**/layout.*',
'bower_components', 'bower_components/**/*',
'data', 'data/**/*',
'.gitignore', 'bower.json', 'readme.md',
'circle.yml', '.bowerrc', 'README.html',
'README.md', 'assets/js/manifest.yml'
]
extensions: [
js_pipeline(manifest: 'assets/js/manifest.yml', out: 'js/main.js')
]
output: 'build'
debug: true
server:
clean_urls: true
scss:
sourceMap: true
outFile: '/'
'coffee-script':
sourcemap: true
jade:
pretty: true
locals:
images_path: '/img'
css_path: '/css'
js_path: '/'
when I comment out the locals and the js_pipeline config, roots watch starts working again and successfully launches local server + opens browser window. Great. What's not so great is having no error messages to determine why this is happening. Is there anyway to get visibility into what's going on inside roots watch?
If it's helpful, I zipped up the project at this point, what's the best way to get it to you?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels