https://github.com/mridang/example-grunt
A reference repository that I use for keeping track of how a grunt project should be set up
https://github.com/mridang/example-grunt
babel browserify eslint grunt jshint lebab mocha prettier uglify
Last synced: about 2 months ago
JSON representation
A reference repository that I use for keeping track of how a grunt project should be set up
- Host: GitHub
- URL: https://github.com/mridang/example-grunt
- Owner: mridang
- License: mit
- Created: 2020-04-14T17:15:50.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2023-02-11T00:35:00.000Z (over 3 years ago)
- Last Synced: 2025-02-05T00:43:32.895Z (over 1 year ago)
- Topics: babel, browserify, eslint, grunt, jshint, lebab, mocha, prettier, uglify
- Language: JavaScript
- Size: 1.25 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE.txt
Awesome Lists containing this project
README
A reference project on how I set up a Grunt toolchain with the following tools:
1. Babel
2. Prettier
3. JSHint
4. ESLint
5. Lebab
# Auditing
``
npm audit fix
``
# Testing
```
npx mocha --reporter=markdown
npx nyc --reporter=html --reporter=text mocha
npx nyc --reporter=html --reporter=text mocha --reporter=markdown
```
## Choosing a Node Version
Use only LTS versions and define that in the `.nvmrc` file
## Updating packages downloaded from the registry
Updating local and global packages you downloaded from the registry helps
keep your code and tools stable, usable, and secure.
### Updating local packages
We recommend regularly updating the local packages your project depends on
to improve your code as improvements to its dependencies are made.
Navigate to the root directory of your project and ensure it contains a
package.json file:
```
cd /path/to/project
```
In your project root directory, run the update command:
```
npm update
```
To test the update, run the outdated command. There should not be any output.
```
npm outdated
```