Hi all, I've run into this problem. If anyone knows how to fix it?
firstname.lastname@example.org start C:\Users\walter\fbasic1
gulp: src\node_contextify.cc:627: Assertion
Error: email@example.com start:gulp`
Exit status 134
at EventEmitter.<anonymous> (C:\Users\walter\AppData\Roaming\npm\node_modules\foundation-cli\node_modules\npm\lib\utils\lifecycle.js:217:16)
at EventEmitter.emit (events.js:182:13)
at ChildProcess.<anonymous> (C:\Users\walter\AppData\Roaming\npm\node_modules\foundation-cli\node_modules\npm\lib\utils\spawn.js:24:14)
at ChildProcess.emit (events.js:182:13)
at maybeClose (internal/child_process.js:961:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:250:5)
Foundation.addToJquery($)still be necessary?
@DanielRuf What I mean is, should
util/unit, since it uses functions from that partial. i.e. You either have:
util/breakpoint depends on/imports
util/unit, and you only need to import
util/breakpoint. (graph-like dependencies)
util/breakpoint doesn't import
util/unit, so if you need to use
util/breakpoint, you have to import
util/unit as well. (flat dependencies)
The way it is now, I have to know what
util/breakpoint depends on, and that may change over time (so code could break, in theory). Also, it's hard to know whether or not it's okay to use
util/breakpoint on its own, vs all of
util/util, vs the whole of Foundation.
However, I don't really know what the norm is in Sass. This is obviously how things work in JS, but that behaves differently as well.