Marcel Greter

It would still be nice to know if the overhead is coming from node or not ;)

Specially since I have no clue how to do profiling on c code when libsass is invoked via node ...

I did a `npm install -g yarn` and that's what I get currently: ``` D:\github-sass\perl-libsass\bolt>cd docs-site && yarn run start yarn run v1.17.3 $ bolt start 'bolt' is not recognized...

Are you sure this works on windows, or do I need to get into my linux server or vm?

The results from linux: ``` git clone https://github.com/bolt-design-system/bolt --branch test/sass-compile-test cd bolt npm install yarn -g yarn install yarn run start yarn run v1.17.3 $ cd docs-site && yarn run...

One more distinct error I got from running `npm run setup` is ``` @bolt/[email protected]: The engine "node" is incompatible with this module. Expected version ">=10.0.0". Got "8.12.0" ```

I don't seem to be able to get this running, updated my node (win) to latest LTE version (v10.16.3), but I still get various seemingly non-related errors, whatever commands I...

OK, now I get a distinct error from node-sass install: ``` Downloading binary from https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-64_binding.node Cannot download "https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-64_binding.node": ``` That file seems indeed not available, not sure why it tries...

After a lot of struggle to get anything to run, I finally got some numbers out, although only by invoking sassc directly by mangling the includes and other code a...

P.s. with a global memory pool and a free-list on top, plus another few tweaks here and there I get the runtime down to 3.5 seconds. Doubling the speed with...