You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 4, 2020. It is now read-only.
Just wondering if you would accept a PR that implements a destination folder option for the generated .vue
I would use that feature since I wish to use 'vgc' inside package.json scripts such as: ... "scripts": { "component" : "vgc process.env.name --dest=./assets/js/" } ...
And call it like: npm run component --name=Home
Hope it was clear enough!
The text was updated successfully, but these errors were encountered:
I assumed that the command would know to put the component in the 'components' folder. Maybe unreasonable - but the terminal gave no feedback / so I wondered if it just didn't work at first. My second thought was to vgc --h - and I expected to see a place to set the destination. If I could run the command from the root - that would be ideal. : )
Hey, your package rocks! 💯
Just wondering if you would accept a PR that implements a destination folder option for the generated .vue
I would use that feature since I wish to use 'vgc' inside package.json scripts such as:
... "scripts": { "component" : "vgc process.env.name --dest=./assets/js/" } ...
And call it like:
npm run component --name=Home
Hope it was clear enough!
The text was updated successfully, but these errors were encountered: