Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
The Jared Wilcurt
@TheJaredWilcurt
@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
Stephen Smith
@chemicaldesign_twitter
It seems to compile when I first start the project but then no further saves after that. I'll try the update.
Thank you.
Stephen Smith
@chemicaldesign_twitter
Sorry. Read through the documentation and really not that confident about actioning this.
The Jared Wilcurt
@TheJaredWilcurt
I wrote a new page with better/clearer instructions. hope that helps
Stephen Smith
@chemicaldesign_twitter
Hi Jarred. That made perfect sense. I went through the instructions and lots happened but when I ran npm start nothing has happened. I have tested Scout again but the problem still persists. I'm happy to paste the code from my terminal is 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:

The Jared Wilcurt
@TheJaredWilcurt
npm install && npm start
run that
The Jared Wilcurt
@TheJaredWilcurt
when you run node -v && npm -v what do you get
Stephen Smith
@chemicaldesign_twitter
v13.12.0
6.14.4
I also ran npm install && npm start
Scout-App is now not starting up :(
The Jared Wilcurt
@TheJaredWilcurt
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
The Jared Wilcurt
@TheJaredWilcurt
you could also try replacing the files in your existing Scout-App version (2.18.16) with the latest downloaded source files
Stephen Smith
@chemicaldesign_twitter
Thanks Jared. I'll give that a go. Thank you for your advice and persistence.
schmause_r
@RSchmause_twitter
Hello everyone, i just started using scout app. Where can i stop it from compiling scss files that i just wan to use for "@import" to stay organized?
The Jared Wilcurt
@TheJaredWilcurt
rename files that you do not want a CSS version of to start with _
file.sass => _file.sass
schmause_r
@RSchmause_twitter
oh, that was fast. thank you
The Jared Wilcurt
@TheJaredWilcurt
those are called "partials"
RussDCA
@RussDCA
I have it installed, have pointed it to my project, have a rudimentary understanding of what to look for, but I'm kind of shooting in the dark really
RussDCA
@RussDCA
It's okay. The one thing I wanted to work out, I think I have sorted
The Jared Wilcurt
@TheJaredWilcurt
:+1:
matthijs-ll
@matthijs-ll
anyone can explain/help me with variable scope?
I have variables in one included file (theme) that I want to use in the next (base)
The Jared Wilcurt
@TheJaredWilcurt
$cow: #F00

.moo
    color: $cow

$cow: #00F !default

.moo
    color: $cow

$cow: #0F0

.moo
    color: $cow

becomes

.moo { color: #F00 }
.moo { color: #F00 }
.moo { color: #0F0 }

There is no scoping. It just uses whatever the current value is stored in the variable

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
matthijs-ll
@matthijs-ll
Thanks. Your example is about inside 1 file, not?
I'm looking for:
base-scss
  • include theme-scss (variable $nicecolor;)
  • include mixins-scss (Where I want to use theme-scss' $nicecolor)
The Jared Wilcurt
@TheJaredWilcurt
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'
Same result
The Jared Wilcurt
@TheJaredWilcurt
@matthijs-ll
Dan Goodspeed
@dangoodspeed
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.
The Jared Wilcurt
@TheJaredWilcurt
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
The Jared Wilcurt
@TheJaredWilcurt
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
Dan Goodspeed
@dangoodspeed
I'm not 100% sure how all the processes work, but Activity Monitor says Scout is running a few subtasks of "nwjs Helper", one of which seems to be using a lot of energy.
The Jared Wilcurt
@TheJaredWilcurt
Don't know what to tell you. if it is a major concern, you may want to switch to an alternative for Sass process. Like using Node-Sass directly, or a tool like Gulp-Sass, Vite, or Webpack
though those approaches all require command line knowledge
but would be drastically fewer resources because they would not have a GUI
Dan Goodspeed
@dangoodspeed
It's fine. I was just checking in to see if you were aware of the issue or anything. I do know the command lines, but I just like the simplicity / visual feedback of the GUI, switching between projects etc.
Izzatiy
@Izzatiy
Hi there, anyone from Scout App admins, i need an access to edit the language i added on the google sheet
Izzatiy
@Izzatiy
@TheJaredWilcurt thanks for sharing. I have it translated into my language and opened an issue on GitHub under the ticket number #428.