-
Notifications
You must be signed in to change notification settings - Fork 36
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
Custom targets for bundled scripts and styles? #76
Comments
I second this suggestion. |
actually this is possible, however poorly documented. You can accomplish this by adding the paths as part of the bundle name in For your use case, it would basically look like this:
So the resulting files would be Please let me know if that answers your question |
Wow that looks to solve the issue 👍 |
Awesome, thanks for the quick reply! I'll try this out. |
It looks like my question is actually a duplicate of #49. Should we add it to the Wiki? |
@alexweissman definitely. want to take a crack at writing up some markdown for documenting this? |
Done. |
@alexweissman perfect! thanks! |
Thanks for the great plugin! This seems like the exact solution I need for a full-fledged asset manager.
This issue relates to #22 and #60. In addition to specifying custom bundle directories in the
bundle.result.json
, it would also be useful if I could specify custom target directories for different types of assets. For example, multiple bundles' Javascript assets could be written topublic/js/
, while CSS assets could all be written topublic/css/
.Is this currently possible?
The text was updated successfully, but these errors were encountered: