These are chat archives for jescalan/roots

9th
May 2016
Tom Kraak
@tkraak
May 09 2016 00:55
I wiped node off my machine and then used nvm to install node 6.1.0
roots watch is still throwing errors
then I installed node 4.4.4 and everything seems to be working!
can’t wait to dig in
thanks again @Leeds-eBooks!
Jeff Escalante
@jescalan
May 09 2016 13:47
hey there @tkraak - glad this was worked out!
i have node 6.1.0 running on multiple machines and roots is still working fine
although after updating to 6, it does add that graceful-fs warning
which i'll be patching up this week
if you can give me more details on which errors are coming up maybe we can work it out!
Tom Kraak
@tkraak
May 09 2016 13:57
@jenius thanks for chiming in! what’s the best way to get you the full error log? just paste it here?
Jeff Escalante
@jescalan
May 09 2016 15:16
yeah surround that in triple backticks
Tom Kraak
@tkraak
May 09 2016 15:17
will do!
Tom Kraak
@tkraak
May 09 2016 17:05
 ~/learn/roots/learn-roots $ roots watch             
(node:13129) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:13129) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
compiling... Error: TypeError: /Users/tkraak/Learn/roots/learn-roots/assets/css/master.styl:8:1
   4| base()
   5|
   6| body
   7|   padding: 50px
   8|
------^

Path must be a string. Received undefined

  at Error (native)
  at on_error (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/lib/cli/watch.js:76:11)
  at Roots.<anonymous> (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/lib/cli/watch.js:53:14)
  at emitOne (events.js:96:13)
  at Roots.emit (events.js:188:7)
  at Compile.<anonymous> (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/lib/api/compile.js:74:20)
  at tryCatchReject (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/makePromise.js:845:30)
  at runContinuation1 (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/makePromise.js:804:4)
  at Rejected.when (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/makePromise.js:625:4)
  at Pendin
g.run (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/makePromise.js:483:13)
  at Scheduler._drain (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/Scheduler.js:62:19)
  at Scheduler.drain (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/Scheduler.js:27:9)
  at _combinedTickCallback (internal/process/next_tick.js:67:7)
  at process._tickCallback (internal/process/next_tick.js:98:9)

Potentially unhandled rejection [6] TypeError: /Users/tkraak/Learn/roots/learn-roots/assets/css/master.styl:8:1
   4| base()
   5|
   6| body
   7|   padding: 50px
   8|
------^

Path must be a string. Received undefined

  at assertPath (path.js:7:11)
  at extname (path.js:1429:5)
  at new SourceMapper (/Users/tkraak/Learn/roots/learn-roots/node_modules/stylus/lib/visitor/sourcemapper.js:41:7)
  at Renderer.render (/Users/tkraak/Learn/roots/learn-roots/node_modules/stylus/lib/renderer.js:94:9)
  at dispatch (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/node.js:71:15)
  at callAndResolve (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/apply.js:30:12)
  at apply (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/apply.js:23:4)
  at Object.call (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/node.js:107:10)
  at Stylus._render (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/accord/lib/adapters/stylus/0.x.js:105:21)
  at Stylus.Adapter.render (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/accord/lib/adapter_base.js:122:19)
  at CompilePass.compile_or_pass (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/lib/compiler.js:522:27)
  at tryCatchReject (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/makePromise.js:845:30)
  at runContinuation1 (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/makePromise.js:804:4)
  at Fulfilled.when (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/makePromise.js:592:4)
  at Pending.run (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/makePromise.js:483:13)
  at Scheduler._drain (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/Scheduler.js:62:19)
  at Scheduler.drain (/Users/tkraak/.nvm/versions/node/v6.1.0/lib/node_modules/roots/node_modules/when/lib/Scheduler.js:27
Jeff Escalante
@jescalan
May 09 2016 17:58
@tkraak ok, can you print roots -v and point me to the repo that you're using to generate this error?
Tom Kraak
@tkraak
May 09 2016 18:43

@jenius … roots version is 4.1.0

I don’t have it in git yet. Can you point me to a good .gitignore starting point before I run git init?

Jeff Escalante
@jescalan
May 09 2016 18:44
node_modules, public, .DS_Store
and any other sensitive files you may have
Tom Kraak
@tkraak
May 09 2016 18:44
:) thx
.gitignore is already there … sorry!
Tom Kraak
@tkraak
May 09 2016 19:04

@jenius … here is the repo:

https://gitlab.com/backroom/learn-roots

Jeff Escalante
@jescalan
May 09 2016 19:42
ok this seems like it's a massive bug'
for now i'd run npm i roots@4.0.1 -g
and use that
i'll have this fixed shortly
thanks for catching!
Tom Kraak
@tkraak
May 09 2016 21:15
@jenius no, thank YOU for your contribution to the static web and making Roots what it is today!
Ben Styles
@benadamstyles
May 09 2016 21:58
:heart:
Jeff Escalante
@jescalan
May 09 2016 22:32
:sparkling_heart:
Tom Kraak
@tkraak
May 09 2016 23:02
@jenius ... will I miss out on anything if I stay on node 4.4.4 with roots 4.1.0 or we should use 4.1.0 at all until the bug is fixed?
not use 4.1.0
Jeff Escalante
@jescalan
May 09 2016 23:03
@tkraak im not entirely sure, i have to figure out what's causing the bug. will only miss out on slightly newer versions of certain compiled languages through accord, not including any of the default languages
I had a meeting today and now have to run, but I will investigate this and release a patch tomorrow probably before the end of the day :)
Tom Kraak
@tkraak
May 09 2016 23:04
thanks!