6to5 (now BabelJS) is becoming the new standard for raw ES6 transpilation, producing more readable code than Traceur. Web essentials should add support for BabelJs by using a configurable extension.220 votes
Babel is now supported in the Web Compiler extension. Download: https://visualstudiogallery.msdn.microsoft.com/3b329021-cd7a-4a01-86fc-714c2d05bb6c
JSPM is supported in the Package Installer extension https://visualstudiogallery.msdn.microsoft.com/753b9720-1638-4f9a-ad8d-2c45a410fd74
It was suggested before, and marked as completed.
But the suggested tools are not working like WE did (compiling less or minifying js when existing files exist), and takes away from the integration my team had when we all used vs 2013.
Yea, gulp/grunt will be better, but for that my team needs to learn it, and for now they just rather stay with vs 2013 and do things like they know how.
Please keep this feature, even as an option that is turned off by default.6 votes
This is now fully supported in the Web Compiler extension. Download here: https://visualstudiogallery.msdn.microsoft.com/3b329021-cd7a-4a01-86fc-714c2d05bb6c
I've tried creating a file besides my web project, without success. I've tried creating a file besides my solution file, without success.
This is a necessary feature since we want to tweak the rules in a team environment.3 votes
This is now supported by the Web Linter extension. Download here https://visualstudiogallery.msdn.microsoft.com/6edc26d4-47d8-4987-82ee-7c820d79be1d
Less compilation should continue to work for older asp projects. ie not asp vnext..
I cannot find any way to compile the less files in these.22 votes
Use the new Web Compiler extension for Visual Studio 2015 to compile LESS, Sass and CoffeeScript files. Download here https://visualstudiogallery.msdn.microsoft.com/3b329021-cd7a-4a01-86fc-714c2d05bb6c
This was fixed with the Web Compiler extension for VS2015. https://visualstudiogallery.msdn.microsoft.com/3b329021-cd7a-4a01-86fc-714c2d05bb6c
I have 2 questions.
1) Is there a plan to provide the ability to invoke Web Essentials features via MS Build? If so when would this happen. In my opinion this is an important feature. For example we would like to treat the output of the JS bundles like we do DLLs and not check in that auto generated output. At this time we are forced to check it into source control and trust that when developers check in their JS changes that they also check in the minified JS changes as well which I think is a risk. I could forsee us breaking production code because it is easy to read the JS changes but not as easy to vette minified output of bundling.
2) In the interim if the solution is built with devenv will that invoke the Web Essentials extension? If it does do you see any downsides to that approach instead of using MS Build?
I have 2 questions.
1) Is there a plan to provide the ability to invoke Web Essentials features via MS Build? If so when would this happen. In my opinion this is an important feature. For example we would like to treat the output of the JS bundles like we do DLLs and not check in that auto generated output. At this time we are forced to check it into source control and trust that when developers check in their JS changes that they also check in the minified JS changes as well which I think is a risk. I…12 votes
For VS2015 you can now call bundling, minification and client-side compilers from MSBuild. See Web Compiler https://visualstudiogallery.msdn.microsoft.com/3b329021-cd7a-4a01-86fc-714c2d05bb6c and Bundler & Minifier https://visualstudiogallery.msdn.microsoft.com/9ec27da7-e24b-4d56-8064-fd7e88ac1c40
Right now, the only way to accomplish this is to create a solution level item. While this is good in its own way, it also is a pain point to do this for every solution. Further, it creates an extra solution item that is not related to the actual code. On one hand it allows easy propagation of settings but on other hand, forces you to create them even if you don't want to enforce it.
Would be nice to have a global stylesheet which can be overridden by a solution specific one, if needed.6 votes
It would be awesome if GFM was supported, including task lists.
Thanks for all your hard work!14 votes
WE 2015 now uses CommonMark.NET
I know it is early days for Aurelia, but I think it has great potential, and any support early on would be a great help.3 votes
This is included in WE 2015 and more support is coming
Web essentials doesn't install to VS Express 2013 for Web Update 4 for now, and if I edit extension.vsixmanifest and install it anyway - it crashes Visual Studio.15 votes
v2.5.2 now supports Express
It will be nice to have ability to recompile bundles on the server with some kind of simple command line tool without need to install visual studio and web essentials.96 votes
You can now use Bundler & Minifier for VS2015 which has MSBuild support https://visualstudiogallery.msdn.microsoft.com/9ec27da7-e24b-4d56-8064-fd7e88ac1c40
The current browser link toolbar that appears at the bottom of the page fails the WCAG2 accessibility tests because the two images in it don't have alt tags. This causes 2 errors when checking locally for compliance using HTML_CodeSniffer ( http://squizlabs.github.io/HTML_CodeSniffer/ ). It would be great if alt tags could be added so these errors don't occur.
Or even better, combine accessibility checking in Web Essentials3 votes
Trying to utilise the new map data structure but it won't compile.
Don't really know how it all works but I assume the Sass compiler bundled in WE is out of date? If so would be great to see an update.
$map: (key1: Red, key2: Green, key3: Blue);
background-color: map-get($map, key1);
Which should result in:
Node-Sass should now support it. WE 2.5.2 now also includes the option to use the official Ruby based Sass compiler
Fiddler has a new feature that can show you images have have a lot of bloat. Metadata and poorly compressed files are everywhere. It would be nice if Web Essentials could scan your project for these files and potentially fix or offer suggestions for issues it finds.3 votes
Web Essentials 2013/2015 comes with a context menu button for optimizing images. It does that using industry standard tools like PngOut, OptiPng, JpegTran, GifCicle etc.
Base64 image conversion was created for CSS url but it was not included in for <img src="foo.svg usage.
I believe it should be added for consistency sakes.8 votes
This exist for HTML and Razor files but not for WebForms
with the advent of the wonderful autoprefixer, now that I don't need to put all the vendor specific CSS rules in, I have zero need to see browser compatibiity warnings in the editor ("Add missing vendor specifc properties...). Please add an option to turn this off, since it is no longer needed with autoprefixer enabled.27 votes
Implemented in WE2015
This allows people to write framework/library-specific rules or team-specific rules that wouldn't be implemented by more general purpose tools like ESLint.76 votes
ESLint is now available in the Web Linter extension https://visualstudiogallery.msdn.microsoft.com/6edc26d4-47d8-4987-82ee-7c820d79be1d
The JSX editor is included in Visual Studio 2015 RTM and will have even more features and tweaks for Update 1. Thanks for everybody who voted for this feature!
It would be great to be able to generate RTL version of project CSS files (on build or on save), I would suggest using RTLCSS: https://github.com/MohammadYounes/rtlcss58 votes
- Don't see your idea?