-
-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File globbing #49
Comments
👍 |
Please give this higher priority. As @kamranayub mentioned, it will be better if we could just specify configurations for *.less. |
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. |
Yes, this is pretty much a must-have feature |
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. |
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? |
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:
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:
or something very similar to this? |
@DoctaWorm That's the plan |
Would really like this (no need to bundle) |
Hi, |
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. |
Please see pull request #199 for one possible implementation of this. |
Would love this feature. |
Unfortunately, So it seems sending a PR isn't an option :/ |
+1 |
Starting to think this will never get implemented. |
This would be really really useful. |
There is a PR here, #317 but dunno what the next step there. Not sure if the checklist is mandatory |
Any news here? Apparently globbing is shunned because or scss load/compile order. I had to create a single file with a list of imports to get this to work the way i wanted. |
Adding each file manually and adjusting the options for it is really tedious. |
My solution to this was to have a single .scss file that contains imports. :/ |
Has this been resolved? I'm in need of the glob and I don't find a solution anywhere. I try to define the stylesheets from a JSON object, and would like to not have to set each file within a specified folder for each theme needed. |
@Marcelx8 this fork / new implementation implements a Hope that helps |
@stefanloerwald Thanks for the quick reply. I will update you when I got it to work! |
Without glob support this extension is useless. |
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:The text was updated successfully, but these errors were encountered: