File globbing

[kamranayub]

It feels like this should support file globs. I have about 12 LESS files in a pages directory that all need their own individual compiled files. Right now I think I need to manually add a JSON entry for each one. I'd rather do something like:

  {
    "files": "Content/pages/*.less",
    "minify": {
      "enabled": false
    },
    "includeInProject": true,
    "sourceMap": false,
    "options": {}
  },

[emrekilinc]

👍

[ashrafsabrym]

Please give this higher priority.
In Web Essentials 2013, every time I save a .less file, it's auto-compiled.
Now in Web Compiler I have to add an entry for every single file. My project has a very large number of LESS files, and they needn't have specific compilation configuration for every single file.

As @kamranayub mentioned, it will be better if we could just specify configurations for *.less.

[justindyer]

I forked the project and added support for *.less syntax. You can take a look at it below. It feels a little primative, but it works. I am not sure if it is pull request quality.

https://github.com/justindyer/WebCompiler

[riipah]

Yes, this is pretty much a must-have feature

[madskristensen]

The challenge here is to make source maps work when the output is combined to a single file. I'm not sure how I should do that. I can easily combine multiple files into one and then run the compiler. The problem with that is that if the compilation fails, I can't show the correct error in the Error List since it now all points to the combined file instead of the individual source file that contains the error.

[Mikey1982]

You could run the compiler for each file and then combine the output...

For my case i need an output file for each less file with x.less to x.css convention. Is that possible?

[DoctaWorm]

To add to this.

Could wildcard support be added to compiling javascript files from ES6 to ES5?

Right now I have a rule in my text editor for es6 to be a javascript file so the compilerconfig.json starts to look like this:

  {
    "outputFile": "App/modules/repeaty/repeaty.js",
    "inputFile": "App/modules/repeaty/repeaty.es6"
  }
  {
    "outputFile": "App/modules/document-viewer/document-viewer.js",
    "inputFile": "App/modules/document-viewer/document-viewer.es6"
  }

Now the larger this project gets the larger this json file is going to get and it's gonna look cluttered.

Is it possible to have a simple solution of:

  {
    "outputFile": "App/*.js",
    "inputFile": "App/*.es6"
  }

or something very similar to this?

[madskristensen]

@DoctaWorm That's the plan

[304NotModified]

Would really like this (no need to bundle)

[forforeach]

Hi,
Any news on this topic?
Thanks

[resnyanskiy]

It could be a very useful feature. I agree that there is some ambiguous situations because we shouldn't bundle files, but as for me the bundling doesn't need here. Looks like the most convenient way is to add 'inputDirectory/outputDirectoy' settings, as it done in #142. If we re-use 'inputFile/outputFile' it would create inconsistent/unexpected behavior or will copy BundleMinifer functions to WebCompiler and we go back to old almighty WebEssentials.
@feherzsolt, FYI.

[mrcrowl]

Please see pull request #199 for one possible implementation of this.