Website Essentials 2015 WebEssentials-Settings.json?

In Web Essentials 2013, you can enable Web Essentials settings in a .json file (exactly named WebEssentials-Settings.json) at the solution level to make sure everyone working on the project uses the same settings. One of the best aspects of this is that it can be saved in version control, and you could impose things on your team how to automatically launch JSHint on build.

Is there a way to achieve this behavior (common parameter definitions stored in the source control) in VS 2015 using Web Essentials 2015?

At least at the time of this writing, Web Essentials seems to have refused support for the .weignore file (see Basic Web Resources - General Features and switch the drop-down list of versions from 2013 to 2015) ... I hope the settings file also will not disappear.

+4
source share
1 answer

WebEssentials solution options:

It looks like the file name and structure changed in WE 2015 (which makes sense to see how the feature set has changed).

You can create a file WebEssentials2015-Settings.jsonby clicking on the link:

"Web Essentials> Create Solution Parameters" in Visual Studio 2015.

Create solution settings

WebEssentials2015-Settings.json

Web compiler configuration:

-, , compilerconfig.json compilerconfig.json.defaults, .

- - .

:

compilerconfig.json

compilerconfig.json , .

, :

[ { "outputFile": "output/site.css", "inputFile": "input/site.less", "minify": { "enabled": true }, "includeInProject": true, "options":{ "sourceMap": false } }, { "outputFile": "output/scss.css", "inputFile": "input/scss.scss", "minify": { "enabled": true }, "includeInProject": true, "options":{ "sourceMap": true } } ]

compilerconfig.json compilerconfig.json.defaults .

CompileOnBuild:

NuGet "BuildWebCompiler". - "-p > ..." , , LSS, Sass, JSX CoffeeScript Transpilation, Web Compiler, .

Enable compilation during assembly ...

(: , , "CompileOnBuild" , NuGet "BuildWebCompiler" NuGet).

+3

Source: https://habr.com/ru/post/1624986/


All Articles