Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature: WEIgnore (#589) #1250
The docs should go to http://www.github.com/madskristensen/vswebessentials.com/ which would eventually appear at http://www.vswebessentials.com/.
That said, it supports all styles supported by
Currently it only targets nodejs pipeline services, meaning TypeScript compilation (not TSLint) and Markdown are out. For markdown, we would probably shift to nodejs-based marked compiler, once this feature is implemented.
It works just like
How it works:
The first config file that is found in the aforementioned chain takes effect. All the file-path patterns inside the
Note: The space between
Here is the list of all the (node-based) compilers and linters currently supported by WE:
The parent list items are referred as "service-categories" and sub-list constitutes "service-names".
Advanced Usage (going crazy):
You can have negation for service type and service names as well!
It will only ignore autoprefixer.
will not ignore coffeescript compilation, because the negation of pattern will take precedence. We can implement this logic, if its really desired. Meanwhile, it is recommended to keep your logic simplified (see this Wolfarm|Alpha's logic expression simplifier).
As describe above, it first skips the negative patterns (those starting with exclamation mark
Then it looks for service-category or service-name. If none is found, it moves on to test the pattern match.
If there was tab-separated service category/name specified on the line, before matching the pattern, it checks if the caller service needs to be ignored (or that it has
Take it for a spin with v2.2.3+ ........
Multiple negations in .weignore file
I want to produce two distinct css files from what I have in less folder. So I made a .weignore file such this:
It didn't work out. It produces bootstrap.css but not bootstrap-cosmo.css