I would previously have rated this 5 stars, but this latest version runs the "linter" on every build, which basically kills my development environment on any project of any size. There does not appear to be a way to prevent it from running on minimized files.
You can turn this behavior off in the options, otherwise I would have to disable this extension entirely.
Freezes Visual Studio completely when I have knockout attributes in the HTML.. Have to terminate VS and restart over and over again.. The web essentials is disabled until this is fixed.. I really hope you work on this.
This add-in is great in VS2012, except for one problem: most of the time when I try to save a .coffee file that has syntax errors, Visual Studio crashes. Let me know if there is any info I can send to help you debug this.
Really great ideas, but JS extensions are way too slow and seem to compete with MS JS extensions, which are better. Can you add the ability to selectively enable/disable the tools? That might be a huge improvement. The CSS extensions are awesome, but I can't leave this thing running because it kills the JS editor.
WE is great.. but
Using VS2013 Rc I am getting too many false positives.
In js its telling me that variable is defined but never used, but is used in another script or in say a ajaxForm success call.
In css its telling me heaps of rules are unused when they are used.
This makes a huge unmanageable list of warnings
When I open a less-file, WE automatically tries to compile it, and therefore any errors in the compilation is added to the error list. Since I haven't initiated the compile myself, I think that the result of the "helpfull" compile should just be warnings, if anything.
When I do compile/save the file, it is fine to add the results to the error list.
I have been getting this error while working with TypeScript files in VS 2012. I have options to generate js turned on. As soon as I make an edit to .ts file and hit save, the error "Error writing file" comes up in the js window. Workaround includes checking out all ts/js files or just turn on the option to build all ts files during project build.
Any chance for this to be fixed?
I'm using the RaphäelJS library on my project and JSHint issues too many errors for this library.
I've tried to create a .jshintignore on my project, without any success.
There is some way to ignore certain .js files from JSHint build validation?
Any chance to make .jshintignore to work?
why doesn't @import work right with absolute paths?
in my root .less file I have:
but in the error list it says:
Error 31 LESS: Couldn't load Content/bootstrap/less/reset.less (404) ...
NOTE the lack of a leading '/' - it got removed.
I opened a website (File > Open > Website) from a local directory. Then added new CoffeeScript file using new file dialog (Ctrl+N). The new coffeescript editor is opened with preview split screen.
Then pasted this coffee code in it http://pastebin.com/Hzt4gBtE. Once pasted, I clicked in preview screen (for JS), I got the shutting-down error.
Please review this issue. I just updated to v2.7..
Please also bring the CoffeeScript and other filetypes in new file dialog when no project or website is opened (open a new instance of VS and press Ctrl+N).
PS Its a shame that we don't have support for SCSS and SASS!
I've started facing an issue after I upgraded to version 1.6 where the @import url('../../../settings.less'); stopped working and I see the following error in the output window
Error 1 LESS: Couldn't load ../settings.less (404)
Is this a known issue? Is there a workaround?
I'm using Twitter Bootstrap (less version) and even though the compilation result is OK, while in edit mode on the .less file the // comments show a syntax error. For example "// Core variables and mixins" this would trigger an "unexpected token" syntax error. Is that a known issue?