create-nuxt-app VS lint-staged

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:

lint-staged is the second important tools we need here, install it via NPM.

We were already using lint-staged and have a pre-commit hook in place using Husky in our project for linter and prettier. So it made sense to add a check here.

Now you can config it in your package.json, here is the guide doc:

In the world of software development, maintaining consistent code quality and ensuring that the codebase adheres to predefined patterns and guidelines is crucial. However, manually enforcing these standards can be time-consuming and error-prone. This is where automation tools like Husky, Lint-Staged, Commitlint, and Commitizen come to the rescue. In this post, we will explore how these tools can be combined to streamline your development workflow.

This is wasted work that can and should be automated. Adding a linter and formatter on CI and a pre-commit hook such as lint-staged can do wonders.

lint-staged is a package that can be used to run formatting and linting commands on staged files in a Git repo.

To answer your next question: I lint and format on save, and I use Git hooks installed by Husky and executed through Lint-Staged (this tool helps ensure your Git hooks only run on modified files, etc) to ensure there are no lint or formatting errors whenever making a commit or pushing code. This is helpful for teams, as some developers tend to forget to run lint tasks, or don't have the Prettier extension installed in their IDE. If there are lint errors, the commit is rejected until fixed. YMMV - you'll need to fine-tune the strictness of this based on the team's needs.

Uses Husky Git hooks and Lint-staged pre-commit hooks.

Something else to consider is applying linting and formatting before every git commit. A package like Lint-staged only lints and formats on staged items, ensuring all pushed code follows the standards in the repo. This allows developers to have their own formatting preferences when developing, while the code homogenizes on push. Linting pre-commit also avoids strict rules like no-console or no-unused-vars restricting a developer when writing code, when it should only apply in production. Imagine not being able to console log anything during development!

Lint-Staged Docs