Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Vue js component generator
Features
Note that this package is published under name of
vue-gue
npm i -g vue-gue
Head over to root of your project in terminal, say you want to create a component named footer
:
gue footer
This will generate footer
component in ./src/components/footer.vue
You can define a directory which you want your component to be generated in.
gue tab ./menu
This will generate tab
component in ./menu/tab.vue
Consider behavior of directory parameter when you have a config file and you don't. details
For a consistent way to change root directory of components see config.
Now if you want a component and also it's corresponding unit test file you can do:
gue footer -u
This will generate footer
component in ./src/components/footer.vue
and also a test file in ./tests/unit/footer.js
To change any of these directories see config
General usage is like:
$ gue --help
Usage: gue <componentName> [direcroty] [options]
Options:
-u, --unit create unit test of the component too
-t, --template <name> define which template to use
-h, --help output usage information
subdirectory
of your componentRoot
If you don't, then this will lead to generation of component in exact direcroty
-u
which will generate test file, and -t
which is used to define which template for components to use.Gue accepts a config file to change default settings. In root directory of project make a file gue.json
, and Gue will automatically recognize and use it.
Here are available options for config file:
componentRoot
: root directory which components will be generated in. should be relative path.componentSource
: path to custom component template. Or an object to define multiple templates.unitRoot
: directory which test will be generated in. should be a relative path.unitSource
: path to custom test file template.An example of a config file with all options:
{
"componentRoot":"./front-end/src/components",
"unitRoot":"./front-end/test",
"componentSource":"./myTemplates/myVueTemplate.vue",
"unitSource":"./myTemplates/myTestTemplate.js"
}
Now if you run gue to create a clock
component in your project, it'll generate it in ./front-end/src/components/clock.vue
.
If you run following command in the same project:
gue title ./header
Will generate ./front-end/src/components/header/title.vue
As said you can use custom templates in Gue, define path to them with componentSource
and unitSource
so that Gue will use them instead of it's default ones.
In your component template you can use variable <%NAME%>
and Gue will replace it with name of component when generating.
And also in test template you use <%NAME%>
and <%PATH%>
which will be replaced with path where component is located, relative to path of test file.
Here is an example of custom component template:
<template>
<div class="app">
Hey I'm a component generated with Gue, my name is <%NAME%>
</div>
</template>
export default {
name: "<%NAME%>",
data() {
return {
someData: "a sample"
}
}
<style scoped>
</style>
To see other examples look at templates folder.
You can use multiple custom templates. So componentSource
can be object (multiple templates) or a string (single template). Multiple templates can be created like:
{
"componentSource": {
"component" : "./tmps/component.vue",
"page" : "./tmps/page.vue"
}
}
And when using Gue you have to tell it which component template to use:
gue menu -t component
gue setting ./pages -t page
You can define one of your templates as default
one, so that you don't have to type -t
every time. Default component can be specified with :default
postfix:
{
"componentSource": {
"component:default" : "./tmps/component.vue",
"page" : "./tmps/page.vue"
}
}
Now if you type any command without -t
, component template will be used.
gue foo
Will use component
template to generate foo component. No need of -t component
FAQs
Vue component generator
We found that vue-gue demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.