Is there a way to add Jade support in WebStorm's Configure Inspections?
You can get to Configure Inspections by clicking on the Yeoman lookalike in the right below corner
Jade plugin is active, but no Jade in Configure Inspections:
Which is annoying because when you have a jade template with invalid syntax (forgotten comma):
button(type='button' class='btn btn-primary')
WebStorm does not complain, but I get a nasty error when compiling the template. It would be easier to detect such errors faster.
The Jade plugin has no hidden features that have to be enabled in magical ways; the error highlighting you want is simply not implemented in the current version. You're welcome to file a feature request at http://youtrack.jetbrains.com/
Using the new "File Watchers" feature in the latest EAP it's possible to have WebStorm automatically compile Jade as you change the file. It will show errors in the output window as soon as they are detected.
Related
I am on Manjaro using Neovim and SpaceVim vanilla installations. The editor works fantastically well.
Since I am new to vim-style editing, I do not want to mess my configuration. Yet I'm not very savvy about how to add plugins to Neovim+SpaceVim.
I want my Hugo files to have a proper syntax highlighting. Files's content are TOML (.toml), markdown (.md, but not .markdown), Go+HTML (.html with some Go templates inside) and CSS (.css).
I tried to use the vim-go plugin using yay package manager, but there was no syntax highlighting :(
If you could help me, please take into account that I'm very new to this vim-universe. Thanks!
I get this annoying dialog when my SCSS is compiled by sass ruby gem.
How do I disable it?
I solved this simply by removing the folder which contains the compiled assets from Chrome's workspaces. I never quite saw the point of having compiled assets in there anyway, and it gets rid of the dialog.
While i can hot reload XML in Nativescript i am unable to hot reload JS changes. Is this even possible?
I run 'tns livesync ios --emulator --watch'.
My editor is Visual Source Code and I use the NS plugin for it.
Thanks!
NativeScript itself does not yet support hot-reloading of JS files as of version 2.20.
There is a plugin called nativescript-liveedit that allows hot reloading of JS on the Android platform. The plugin is not "perfect" but; it works in the majority of the cases and allows you to configure related files and files to auto-restart on (i.e. if you change a singleton)
(Disclaimer: I'm the author of the plugin)
I am trying to set up the mapping feature in Chrome canary. I followed the screenshots in this answer.
The main feature works, when I inspect an element, it points me to my local sass file and when I edit it, the local file safes, and the `sass --watch' is triggered. However, the browser does not refresh, even though on the "General" tab in devtools I have checked "Auto-reload CSS upon Sass save".
Should the browser reload? Is there a way to get it to reload?
Ps - I have compass but I can not use that as it does not support mapping, so I am compiling sass through the terminal
Thanks
You probably forgot this step:
In the Sources tab, find your generated CSS file, right click on it and choose Map to network resource, and select the same file name in the shown dropdown:
and then choose the matching file from your workspace:
It could be that the Sass-file is still compiling when Chrome tries to reload the CSS. Setting the 'Auto-reload CSS upon Sass save' Timeout to 5000 ms fixed it for me. When Chrome triggers the reload, it can even prevent Sass from recompiling the CSS.
I solved the problem by installing tincr extention and now when I save locally, the browser refreshes.
Often times I use "edit css" functionality in web developer extension to edit my style sheets.
It's a great feature but it takes time to edit the css and copy it back to an editor to save it.
I am planning to use Compass for my next project and I am wondering how I can use "edit css" functionality with SASS/Compass.
There's no way to do this the way you're expecting.
The flow will have to work like the following ->
Write Compass/SCSS -> Refresh Page -> Edit CSS to get results -> Re-Edit SCSS with previous step and or copy/paste.
Because it compiles down, there's no solution I know of yet that hooks it back in to the SCSS layer.
I don't think it will be much different from what you're doing now..
Compass will precompile the stylesheet written with Sass/SCSS, it will be a regular stylesheet by the time it reaches the browser, so if you then use the "edit CSS" function of your browser toolbar it will work the same way as you do now only you will need to go back to the SASS/SCSS file and insert the changes into the right place (e.g. it could be in a nested rule or mixin or function, depending on how you've written the SASS/SCSS file) - then Compass can recompile the stylesheet
Codekit
Codekit is a great product for OSX that will allow you to edit your local files and as you hit save it will automatically inject the new compiled stylesheet into your browser without a page refresh, so it will at least save you that step. However, as of yet there is no Windows counterpart that I'm aware of.
I've used Codekit on a pretty large project recently where we were using SCSS and it was certainly helpful. Although sadly, like you, I'm used to the "Edit CSS" Web Developer Toolbar workflow, and I've yet to find an exact translation over into the SASS world.
Web Putty
One other option that has some potential (but some SERIOUS drawbacks) is a open source framework from Fog Creek called Web Putty. It was a service they offered that allowed you to live edit CSS in the browser, including SASS and SCSS flavored CSS, but they stopped the service and simply open sourced the software so getting it setup is entirely on you and requires quite some effort (THATs the drawback).
This is possible now with experimental support for Sass in the Chrome dev tools.
First enable the support for Sass:
Then make sure you're compiling to anything other than compressed and enable debug info in Sass. If you're compiling from the command line, pass the --debug-info flag, if you're using Compass, add this to your config.rb:
sass_options = { :debug_info => true }
Presto, you have access to the Sass source in the dev tools:
Clicking on the line number in the dev tools will allow you to edit and apply the local changes:
Personally, I prefer to use compass watch in conjunction with LiveReload and edit in my editor, but for those of you that like to edit in the browser, you can now edit the Sass files directly.
Don't forget to compile to compressed before deploying.