create-nuxt-app VS commitlint

I was hoping for https://github.com/nuxt/create-nuxt-app but it does not support Nuxt 3.

Nuxt.js (npx create-nuxt-app my-app)

To get started quickly, you can use create-nuxt-app. // https://github.com/nuxt/create-nuxt-app

Hi! I want to create a small NPM package with whom I can create a project with the settings or libraries I want. create-nuxt-app is similar to what I want to achieve. (See below for the example.)

Github issue

What are you trying to archive here? npx help gives you that error because that package hasn't any executable (https://www.npmjs.com/package/help). If you check the package.json of that package, there isn't any "bin" definied. So npx doesn't know what to execute. See for example https://github.com/nuxt/create-nuxt-app/blob/master/packages/create-nuxt-app/package.json (or run it with npx create-nuxt-app example), which will execute this file https://github.com/nuxt/create-nuxt-app/blob/master/packages/create-nuxt-app/lib/cli.js (see package.json -> bin).

You’ll be asked a couple of questions such as the name of the projects, linter, testing framework etc. Keep the app simple and go with the default options provided. To learn more about the options, head over to Create Nuxt App.

You can start a new Nuxt project easily with create-nuxt-app. This CLI provides an interactive menu for quickly setting up your project.

To get started quickly with nuxt, I've used the yarn create nuxt-app command. After executing the command, I chose the following configuration options:

commitlint is the most important tool we need for this step.

Apart from these we also need to enforce standards for all our commit messages(commit-lint).

There are many features of commitlint that I can't mention one by one, as well as installation guide. To know the detail you can directly access https://github.com/conventional-changelog/commitlint.

These commit message prefixes can help to provide context and organization in a project's version control history, making it easier to understand and track changes over time. Note: if you want to force these rules on commit messages, here is a commit linting lib for you. Commitlint

Commit Lint

I personally find it quite useful to enforce a uniform commit style. commitlint pairs well with husky.

⧗ input: Set up Conventional Commits using Husky and commitlint ✖ subject may not be empty [subject-empty] ✖ type may not be empty [type-empty] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint husky - commit-msg hook exited with code 1 (error)

Can setup tools like Commitlint to add hooks that will reject a commit message if it is invalid, but if you format a commit message incorrectly it simply closes the commit buffer and returns to git status, meaning you have to retype out your commit message, which is obviously less than ideal.

✅ Angular 14 ✅ Angular Material ✅ Unit Testing with Jest ✅ End-to-End Testing with TestCafé ✅ Internationalization with Transloco ✅ Auto documentation with Compodoc ✅ Analyse your project with source-map-explorer ✅ Docker ✅ ESLint ✅ Prettier ✅ Commit Linting