Current script order is alphabetical:
{
"scripts": {
"build": "next build",
"dev": "next dev --turbopack",
"format": "prettier --write .",
"lint": "next lint",
"prepare": "simple-git-hooks",
"registry:build": "shadcn build",
"start": "next start"
}
}
Should be:
{
"scripts": {
+ "dev": "next dev --turbopack",
"build": "next build",
+ "start": "next start",
- "dev": "next dev --turbopack",
"format": "prettier --write .",
"lint": "next lint",
"prepare": "simple-git-hooks",
"registry:build": "shadcn build"
- "start": "next start"
}
}
dev should always be above build, start is followed by build, there are many other considerations, saw a pull request assigning score to script keys #171 by @bluelovers, something like this should be implemented
Current script order is alphabetical:
{ "scripts": { "build": "next build", "dev": "next dev --turbopack", "format": "prettier --write .", "lint": "next lint", "prepare": "simple-git-hooks", "registry:build": "shadcn build", "start": "next start" } }Should be:
{ "scripts": { + "dev": "next dev --turbopack", "build": "next build", + "start": "next start", - "dev": "next dev --turbopack", "format": "prettier --write .", "lint": "next lint", "prepare": "simple-git-hooks", "registry:build": "shadcn build" - "start": "next start" } }dev should always be above build, start is followed by build, there are many other considerations, saw a pull request assigning score to script keys #171 by @bluelovers, something like this should be implemented