Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
grunt-init-pack
Advanced tools
Changelog
0.3.0 / 2016-03-24
Readme
grunt-init template for a project that can have Node package and optionally Bower, Component, Duo, Jam and/or UMD package. Includes JSHint, Mocha+Chai tests, JSDoc (optionally).
If you haven't already done so, install grunt-init.
npm install -g grunt-init
Once grunt-init is installed, place this template in your ~/.grunt-init/
directory.
It's recommended that you use git clone
to install this template into that directory as follows:
git clone https://github.com/gamtiq/grunt-init-pack.git ~/.grunt-init/pack
(Windows users should use %USERPROFILE%\.grunt-init\pack as the correct destination directory path)
To force grunt-init
to use custom default values, move the defaults.json
file to your ~/.grunt-init/
directory,
and customize the values in that file.
Note: you can make the template available as any name you choose by simply changing the name of the folder
that the template is installed into. So instead of ~/.grunt-init/pack
, you may change the name to ~/.grunt-init/foo
so that the template can be used with the following command: grunt-init foo
.
Also you can clone the template into any subdirectory outside of ~/.grunt-init/
directory. For example:
git clone https://github.com/gamtiq/grunt-init-pack.git path/to/grunt-init/templates/pack
In this case you will have to specify path to the template when running grunt-init
(see below).
At the command-line, cd into an empty directory, run this command and follow the prompts.
grunt-init pack
Or
grunt-init path/to/grunt-init/templates/pack
when the template was placed in subdirectory outside of ~/.grunt-init/
directory.
Note that this template will generate files in the current directory, so be sure to change to a new directory first if you don't want to overwrite existing files.
You might want to test that it works before you begin customizing the project:
npm install
to install the project's dependencies; it is necessary only if you have answered no
to the corresponding questiongrunt all
to build the project and test that it worksYou can redefine default prompt answers using defaults.json
file
(see here for details).
Below supported prompt names are listed:
name
- project namedescription
- project descriptionkeywords
- project keywordsversion
- initial versionrepository
- project repositoryhomepage
- URL of project home pagebugs
- URL of project issues trackerlicense
- project licenses (SPDX license ID or expression)author_name
- author nameauthor_email
- author emailauthor_url
- URL of author's sitenode_version
- minimal Node.js versionmain
- main filecli
- whether project should have command-line interfacenpm_test
- NPM test commandesnext
- whether project should be prepared for using of ECMAScript 2015 featuresbower
- whether project should have Bower packagecomponent
- whether project should have Component or Duo packagejam
- whether project should have Jam packageumd
- whether project should have AMD package or standalone script filejsdoc
- whether project should use JSDoctravis
- whether support for Travis CI should be addedtravis_badge
- whether Travis CI build status badge should be included into README.md
npm_badge
- whether NPM version badge should be included into README.md
grunt_badge
- whether Grunt badge should be included into README.md
history_md
- to include or not History.md
in the project filesinclude_config
- to include or not package.json
/bower.json
/component.json
in Gruntfile configurationmatchdep
- to use or not matchdep module to simplify loading of plugins in Gruntfilerelease_task
- to include or not release tasks into Gruntfilenpm_install
- to run or not npm install
command automaticallyMIT
FAQs
grunt-init template to create a project that has Node package and optionally Bower, Component, Duo, Jam and/or UMD package. Includes jshint, mocha+chai tests, jsdoc (optionally).
The npm package grunt-init-pack receives a total of 1 weekly downloads. As such, grunt-init-pack popularity was classified as not popular.
We found that grunt-init-pack 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
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.