Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

6 Commits
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

dave-script πŸš€

A lightweight CLI tool to scaffold basic Node.js applications in seconds. Stop rewriting boilerplate and start coding your logic.

1. Usage

You don't need to install this package. Simply run:

npx @davidwilling/dave-script --base

2. Feature

  • πŸ“ Generates standard files such as(app.js, server.js, .gitignore and config.env).
  • βš™οΈ Pre-configures config.env and .gitignore
  • πŸ“ The generated files are standard nodejs files often ignored.

3. Contributing

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

4. Pull Requests & Commit Messages

How to do a PR properly

  1. Push your branch to your fork on GitHub.
  2. Click "Compare & pull request" on GitHub.
  3. Describe your changes: don't just say "fixed stuff." Say "Added a script to generate a `.env.example` file."
  4. Wait for Review: Your code will be read, if possible i'll leave comments, and then "Merge" it into the main project.

5. Standard Commit Messages (Conventional Commits)

Professional teams use a specific structure so that logs are readable: type(scope): description

Type Purpose
feat A new feature for the user.
fix A bug fix.
docs Documentation changes only.
style Formatting, missing semi colons, etc (no code change).
refactor Code change that neither fixes a bug nor adds a feature.

Example: feat: add script to generate logger middleware

Ready for the Code Review ?

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages