Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

aispin/fs

Repository files navigation

πŸ“¦πŸš€ @aotu/fs

Useful file system utilities.

Build Status Codacy Badge Coverage Status NPM Version Badge semantic-release

βœ… An experimental project applying several cool stuffs, a boilerplate for writing new NPM packages.

βœ“ Auto-release with semantic-release

βœ“ Fast Unit Tests with ava

βœ“ Coverage with nyc

βœ“ Automated Code reviews with codacy

βœ“ Elegant documents via jsdoc-to-markdown along with gitbook

βœ“ Scoped NPM package

βœ“ Publish gh-pages automatically via travis-ci

βœ“ Semantic git commits via semantic-git-commit-cli

Unit Tests

npm test
// Or the watching mode
npm run test1

Debug

  1. Write a debug file at test/debugs/your.debug.js
  2. Run the debug command
node --inspect-brk test/debugs/your.debug.js
  1. Open the Chrome inspector interface
chrome://inspect/

You will see the files listed for inspcecting.

  1. Add the fs folder to the chrome-devtools's workspace

Docs

The documents are generated by jsdoc(jsdoc-to-markdown) along with gitbook(gitbook-cli) following this guide.

  1. Initial build
npm run docs
  1. Incremental build
npm run docs:build
  1. Watching Mode
npm run docs:serve
  1. Clean the generated docs
npm run docs:clean

Release

The module will be released automatically by semantic-release

About

Some useful file system utilities.

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published

AltStyle γ«γ‚ˆγ£γ¦ε€‰ζ›γ•γ‚ŒγŸγƒšγƒΌγ‚Έ (->γ‚ͺγƒͺγ‚ΈγƒŠγƒ«) /