Skip to content

Use exportsOverride to rename target folders#138

Open
tporadowski wants to merge 3 commits into
yatskevich:masterfrom
tporadowski:master
Open

Use exportsOverride to rename target folders#138
tporadowski wants to merge 3 commits into
yatskevich:masterfrom
tporadowski:master

Conversation

@tporadowski

Copy link
Copy Markdown

I needed to be able to easily customize target folder names in my project to follow convention that uses version numbers in folder names, so that i.e. "jquery": "~2.1.1" (from bower.json) gets installed to "js/jquery-2.1.1" (and not as now to "js/jquery"). This change extends exportsOverride configuration option with packageName naming convention which is run through Handlebars with package's metadata (so one can install to i.e. "js/jquery-2.1.1" based on metadata of Bower packages). I also added dependencies to Q and Handlebars to make it work. You can find more details in updated Readme file.

- exportOverride can now use an extended definition that has
"packageName" naming convention which is run through Handlebars with
package's metadata (so one can install to i.e. "js/jquery-2.1.1" based
on metadata of Bower packages)
- added dependencies to Q and Handlebars
- added unit tests for new functionality, fixed JSHint warnings
- "component.json" files were not added in previous commit due to
.gitignore
@JoseInTheArena

Copy link
Copy Markdown

@yatskevich Is this gonna be merged anytime soon?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants