Is there a way to make a squiggly line go away without changing my code? I understand that there are more vendor prefixes I could use, but if my project is only supporting webkit, I would REALLY like to make that squiggly line go away. Please, please, PLEASE put an option to ignore or even an option to disable "alert for vendor prefixes" in the future.
I firmly believe that any squiggly line that comes up in anything should be able to be removed after user consideration. I know this is a great extension, but just like Microsoft Word doesn't always have better grammar than I do, this extension should take my input.
Thank you for the phenomenal extension and all your hard work!! :)
In version 2.2 you can select which browsers to support and the CSS editor will adjust accordingly with the correct validation and auto-generated vendor specifics. Just right-click in the CSS editor to open the browser selector
There seems to be an issue in the Zen Coding support with lists containing sibling elements. e.g. div>ul>li*5>span+div only adds the nested div to the first li, and not the other 4. Nesting the sibling elements in a container div doesn’t work either (div>ul>li*5>div>span+div).
I would give this 5 stars, but as an licensed Mindscape user, I think I will need to disable WE 2012. The reason is, while I can disable compiling and previewing LESS from WE, it still messes with the syntax highlighting and parsing of the LESS files (since that's what Mindscape does).
Mads, I would give you 10 stars if you could either a) detect Mindscape and prompt/automatically disable LESS handling or b) allow me to fully disable LESS handling in WE options.
It should be noted also, I work on a team, so it would also be nice to save a local set of WE settings or something (which is why I mentioned automatically disabling LESS handling).
Unfortunately, I can't turn off LESS editor support dynamically. We (the ASP.NET team) is shipping the LESS editor officially early 2013. That can't be turned off either. Is there a reason you prefer Mindscape's LESS editor over Web Essentials'?
I've just released new LESS editor component in the nightly build. Try it here: http://madskristensen.net/post/Web-Essentials-nightly-builds.aspx
Local WE settings are supported and so are solution based settings. That was introduced in version 1.9
So far, Web Essentials has been a very useful and productive tool. It makes VS that much better, and I'm surprised half of the functionality isn't already integrated into the core VS application. I like the flexibility of the plugin though and quick responses to bugs and features.
If I enable JSHint and set the indent option to 2 (or any other number), I don't get any JSHint errors. Other options seem to work fine.
If I enable the option by adding the following to the .js file: /*jshint indent:2 */, then it works, but this is not the solution we want as options should be set in one place, not each JS file. Is there a way to get this indent option working without having to set it in each JS file?
Also it reports errors for switch case indentation, which I believe have been fixed in a newer version of JSHint (2.2.0). Are there any plans to update the version of JSHint used by Web Essentials 2012?
Finally Web Essentials 2013 was updated to use the .jshintrc options file, are there any plans of including this in 2012?
When I select Build | Web Essentials | Update All Bundles I receive an error:
The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
I just updated to version 3.3.5 today. Prior to this, the bundles were not updating when a source file changed. They are still not updating and I receive the above error.
I receive the same issue, updating a file does not update the bundled files. This seems to get worse after install update 4 for VS2012. Also, selecting Update All Bundles generates the same error referenced by @jdubsmith
I am using VS 2012 and WE 2012 v3.3.5
I installed visual studio update 4 to see if that would fix it but no luck
I also tried VS 2013 with WE 2013 but it doesnt work there either
It's a great tool, however the current version (3.3.5 with VS2012 update 4 and typescript 0.9.1.1 ) does not created minified js automatically in typescript projects.
I have tried many previous versions of webessentials back to 2.9 and different ways of including the ts and js files into the project, either as DependentUpon liek this
<TypeScriptCompile Include="app.ts" />
or as included on the folder level.
<TypeScriptCompile Include="app.ts" />
<Content Include="app.js" />
When typescript compiles the ts to js, webessentials does not trigger the minification; when I then open the js file and save it manually at some point webesssentials might build the min.js version (eratic as far as I can see), but this will also add the new file to the project tree, from then on webessentials will not update the min.js again. Doing a project rebuild will not automatically minify.
I can reproduce this with the standard typescipt project template.
I just realized, that when manually saving the js file, webessentials will (!) create/update the minified version. But this does not happen when the typscript compiler updates the js file.
This makes it necessary to go manually through all your compiled js files and save them before publishing a release (bundled) project.
Also the js files are not by default included in the typescript project so one first has to include these js files to be able to create the minified versions.
I cannot get a LESS file to minify to .css (and .min.css) in Visual Studio 2013 Premium. I'm using Web Essentials 1.3.1. This was working fine in Visual Studio 2012? Is this a bug? (Note: When I right-click a less file, I see a "Minify CSS file(s)" option, but it's grayed out.)
Having saved ONE FILE (inside of .bundle) WebEssentials saves/updates all other bundles.
11/20/2013 4:23:46 PM: Updating bundle: 1.js
11/20/2013 4:23:47 PM: Updating bundle: 2.js
<here pops an error window about script not found, starting with "/">
11/20/2013 4:23:52 PM: Updating bundle: 1.css
11/20/2013 4:24:16 PM: Updating bundle: 1.js
11/20/2013 4:24:20 PM: Updating bundle: 1.css
If one have over 9000 bundles it will crash everything. Is there a setting to update only *currently* saved bundle-file?
Could be "/" at the beginning of the path related (version 1.3.1 16.11.2013)
It seems as if the version of the coffee compiler included with Essentials is not current. I notice this because up until now we've been using node.js to compile our files. The compiled output of WE seems to include more "safe" local variables and extra spaces you saw from previous coffee versions.
We'd really like to start using WE for compilation but we have a number of users who will still be using node.js on their Macs to compile files. We don't want to have them constantly switching back and forth. Would it be possible to update the version of the included coffee compiler? Better yet, would it be possible to make the compile command an option? This would allow us to specify compilation with node and worry about the coffee version on our own.
It works for me with VS2012 Ultimate with update 3 and v3.0 of web essentials. Initially, it looked like VS wasn't even recognizing the .less file, however, on closing and reopening the file, I got the split view and the generation of the .css and .min.css files also started working.
I just confirmed WHY this is not working. This is also broken with Web Essentials 2013. Our LESS files use the import to import general configuration styles, e.g.,
And then use them later, e.g.,
I commented out all the .mix... imported/pre-configured styles and the CSS file was then updated upon saving the LESS file. Once I re-enabled the .mix... styles, then it hosed again.
Please fix this ASAP as it's a huge hassle. Thanks a lot.
Okay, found more info on this and it looks like it's NOT a WE 2012 or 2013 bug but a change in LESS starting with 1.4.0. Here's the blurb from the 1.4.0 release notes found at http://lesscss.org/#changes
@import-once is removed and is now default behaviour for @import.