These are chat archives for jescalan/roots

26th
Jan 2016
Jeff Escalante
@jescalan
Jan 26 2016 03:38
@marthings yes, because your css file might have dependencies that you import through whatever language it uses, or through whatever bundler you use to make your css. the entire dependency tree needs to be tracked in order to do a single file compile
for example, if you make a change to a jade partial, we would need to know every file that uses that partial and recompile those. same for a layout. and if you make changes to a "mixins" stylus file, we'd need to recompile anything that uses a mixin from that file, or imports it
in the past we tried to do single file compiles, but it led to a lot of bugs
the next version of roots will fully support dependency trees and single file compiles but its not a trivial task. it's in the works now
@k00k going to release a new cut of roots with updated dependencies very shortly that resolves this issue and updates to babel 6
Jeff Escalante
@jescalan
Jan 26 2016 03:44
if you want it now, clone down roots, checkout browsersync branch, run npm link, and you're golden. it's fairly stable
just giving contributors a day or so to review it
also in the new release .js alone will work
im sorry its a little janky right now
i have been abroad for the last year and working only 1 day a week so it's been a tad bit behind. everything will be caught up soon, and we have a new and significantly improved version in the works as well
on the browsersync branch, just use .js and install babel-core to compile with babel
Steve Babigian
@k00k
Jan 26 2016 13:15
@jenius thanks for that. I gave it a shot and I get the following error: compiling... [Error: ReferenceError: [BABEL] /private/var/dev/sandbox/abc/assets/js/main.js: Unknown option: base.js]
Steve Babigian
@k00k
Jan 26 2016 13:26
i just tried installing the ES2015 babel preset via npm and a .babelrc file in the project’s root. Same error. I’ll keep playing and keep you posted if I find a fix.
Steve Babigian
@k00k
Jan 26 2016 15:36
it seems this is coming from accord as it tries to merge the application’s options and pass/render them to the babel adapter. if I console.log @opts in compile_or_pass in compiler.coffee, I see the error pop up after I see it console.log the main app config:
{ config: { meta: { defaults: [Object], home: [Object] } },
  config_js: [Function],
  client_templates: [Function],
  js: [Function],
  css: [Function],
  pretty: true,
  filename: '/private/var/dev/sandbox/abc/views/index.jade',
  _path: '/index.html' }
Potentially unhandled rejection [6] ReferenceError: [BABEL]
 /private/var/dev/sandbox/abc/assets/js/main.js: 
Unknown option: base.config
Steve Babigian
@k00k
Jan 26 2016 15:45
pardon me if I have the wrong end of the stick at all, I just discovered roots yesterday :)
Noel Quiles
@EnMod
Jan 26 2016 21:00
I'm getting this error when I run roots watch after having updated all my dependencies (specifically postcss)
compiling... [Error: ReferenceError: Promise is not defined]

Potentially unhandled rejection [6] ReferenceError: Promise is not defined
  at LazyResult.async (C:\Users\quilesn\Documents\Bitbucket\teach-3.0\node_modules\postcss\lib\lazy-result.js:157:31)
  at LazyResult.then (C:\Users\quilesn\Documents\Bitbucket\teach-3.0\node_modules\postcss\lib\lazy-result.js:79:21)
  at tryAssimilate (C:\Users\quilesn\AppData\Roaming\npm\node_modules\roots\node_modules\when\lib\makePromise.js:750:10)
  at AssimilateTask.run (C:\Users\quilesn\AppData\Roaming\npm\node_modules\roots\node_modules\when\lib\makePromise.js:741:4)
  at Scheduler._drain (C:\Users\quilesn\AppData\Roaming\npm\node_modules\roots\node_modules\when\lib\Scheduler.js:62:19)
  at Scheduler.drain (C:\Users\quilesn\AppData\Roaming\npm\node_modules\roots\node_modules\when\lib\Scheduler.js:27:9)
  at process._tickCallback (node.js:415:13)
any idea what the issue could be? I'm pretty sure Promise should be defined right?
actually this could have to do with Lost Grid...
nope still errors
I would just say "eh I'll use another taskrunner and have it do PostCSS on my output" but ideally of course I want to see why this is happening within roots
Steve Babigian
@k00k
Jan 26 2016 21:08
@EnMod what ver of node?
Noel Quiles
@EnMod
Jan 26 2016 21:21
Ah... v0.10.17
lol
goodness gracious
wait...
is that not an older node?
Steve Babigian
@k00k
Jan 26 2016 21:22
i believe postcss needs newer
postcss/postcss#311
Noel Quiles
@EnMod
Jan 26 2016 21:23
According to the node .msi I just got from their site, I already have a newer node
uh oh
lol
thanks for that headsup
Steve Babigian
@k00k
Jan 26 2016 21:23
np
Noel Quiles
@EnMod
Jan 26 2016 21:56
still reported the same thing after a fresh resintall...found a stray install of node on my system under Emscripten, of all things. Deleted that, and now everything is tip top
Jeff Escalante
@jescalan
Jan 26 2016 22:30
@k00k for this version you need to upgrade to babel 6, sorry i should have mentioned this before!
@EnMod glad everything worked out!
Steve Babigian
@k00k
Jan 26 2016 22:31
@jenius isn’t babel-core = babel6, or i’m not understanding what you mean