Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
architect-init
Advanced tools
CLI tool to help you start a new Architect app by creating all the structure and main files.
CLI tool to help you start a new Architect app by creating all the structure and main files of your plugins.
npm install -g architect-init
Before running architect-init
you must create a config file containing your plugins list.
It's a simple text file with each plugins on a new line.
Example :
firstplugin
firstplugin.secondplugin
thirdplugin
thirdplugin/fourthplugin
With default options (auto structure), this will create the following directory structure :
lib
├─ firstplugin
├─ firstplugin.secondplugin
└─ thirdplugin
└─ fourthplugin
architect-init new
It will then ask you the following questions :
Where is stored your plugins list file ?
Specify the path to your plugins list file created above. Default : plugins.conf
Where do you want to store the plugins ?
The directory where to store plugins. Default : lib/
Do you want sub or dotted dirs for plugins ?
Create package.json file for each plugins (yes|no) ?
Create a default package.json file in each of the created folders. Template of the package.json file is located in tpl/package.json
. Default : yes
Create main file for each plugins (yes|no) ?
Create a main JS file in each of the created folders. Template of the main file is located in tpl/main.js
. Default : yes
Force the creation of files even if they exists (yes|no) ?
Do you want to replace existing (package.json/main) files in directories ? Default : no
architect-init generate <pluginName>
Here is the final structure of plugins with options :
lib
├─ firstplugin
├─ firstplugin.secondplugin
└─ thirdplugin
└─ fourthplugin
lib
├─ firstplugin
│ └─ secondplugin
└─ thirdplugin
└─ fourthplugin
lib
├─ firstplugin
├─ firstplugin.secondplugin
├─ thirdplugin
└─ thirdplugin.fourthplugin
The MIT License (MIT)
Copyright (c) 2013 Leeroy Brun
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
CLI tool to help you start a new Architect app by creating all the structure and main files.
The npm package architect-init receives a total of 2 weekly downloads. As such, architect-init popularity was classified as not popular.
We found that architect-init 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.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.