@chemicaldesign_twitter You can try running the latest source code that has several bug fixes in it, to see if that addresses it. https://github.com/scout-app/scout-app/blob/master/documentation/contributing.md#running-scout-app-locally-for-development
Thank you.
@chemicaldesign_twitter https://github.com/scout-app/scout-app/blob/master/documentation/running-latest.md
I wrote a new page with better/clearer instructions. hope that helps
Last bit from Terminal:
sh: nw: command not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! scout-app@2.18.16 start: nw .
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the scout-app@2.18.16 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
run that
I also ran
npm install && npm start
Scout-App is now not starting up :(
You need Node 11 or below. Node 12 changed the way it handles the file system. This is something that will updated in Scout-App later (to allow it to work with newer Node versions). But for now, you can use something like
nvm (which you'd have to install) to change your node version. Or to uninstall Node, then reinstall it at version 11
file.sass => _file.sass
those are called "partials"
I have variables in one included file (theme) that I want to use in the next (base)
the
!default means, "use this value if this is the first time the variable was defined, otherwise ignore this assignment"
Now this changes in the latest version of dart-sass, with
@use. https://sass-lang.com/blog/the-module-system-is-launched
I'm looking for:
base-scss
base-scss
- include theme-scss (variable $nicecolor;)
- include mixins-scss (Where I want to use theme-scss' $nicecolor)
My example shows Variable Declaration/Class 3 times. you could split each of those into their own files, then have a new file import them in the same order and the result would be identical. the when you import a file, pretend that the import gets replaced by the entire file
@import '_cowF00.sass'
@import '_cowMoo.sass'
@import '_coo00F.sass'
@import '_cowMoo.sass'
@import '_cow0F0.sass'
@import '_cowMoo.sass'
@matthijs-ll
Hi I just started looking into what was killing my MacBook battery so fast, and looking at Activity monitor I noticed Scout uses almost as much energy as my two dozen other apps running combined, and that includes Adobe apps and Safari with at least a dozen tabs open at any given time. Just wondering if you're aware of that and if there's any plans to improve it and if there's anything I can do on my end to limit its energy consumption. I'm already only turning on the one project that I'm working on. Not sure if there's anything else I can do. I do love the app, though.
interesting, the app is pretty idle, it doesn't doing anything when it's just sitting there. When running a project it is using
chokidar to monitor the input folder for any file changes, but I would not expect that to use much battery. Scout-App is actually built on top of a pretty old version of NW.js (older chromium and older node) and should actually use up relatively little resources compared to most modern apps.
looks like another project using
chokidar had some discussions around it's performance, gruntjs/grunt-contrib-watch#429
So it may be related
I primarily develop on Windows, where it's CPU is a flat 0%, even when monitoring a project. and the ram usage doesn't fluctuate at all. It's possible that it could be less efficient on OSX, but I would be surprised, as it really doesn't do much if you aren't actively clicking on stuff or having it process sass files, and even then, it's pretty optimized
though those approaches all require command line knowledge
but would be drastically fewer resources because they would not have a GUI
@TheJaredWilcurt thanks for sharing. I have it translated into my language and opened an issue on GitHub under the ticket number #428.