-
Notifications
You must be signed in to change notification settings - Fork 394
Simplify front end file inclusion #146
Comments
@sarahjean Could you be more specific? The current patternset for files.frontend is:
This is including JS and is excluding a number of common third party directories. What is your goal? What should be excluded or included and why? |
@grasmash Yes, currently it grabs any and all JS, I am suggesting that it specifically look at JS provided by the theme, in a /js or /scripts folder, that way this doesn't need to be modified to exclude JS that might be in locations other than that which might not need to conform to Drupal Coder conventions (third party libraries, additional gulp or grunt files, code in node_modules, etc...) |
@grasmash A slightly better version:
Not excluding node_modules caused some local performance issues when trying to run |
It seems odd that we should need to exclude node_modules. Was your node_modules dir nested under a js dir? |
@grasmash No, actually. I'm not sure what was happening there. I think bigger picture it'd be good if this list could be updated via project.yml. |
In filesets.xml, could we do something like this:
So that we are going more specifically for theme js files and not ones that might exist in other folders?
The text was updated successfully, but these errors were encountered: