Skip to content

Commit

Permalink
chore: remove husky (#28)
Browse files Browse the repository at this point in the history
* chore: remove husky

* fix: update hook code

* fix: update hook code

* fix: update hook code

* fix: update hook code

* refactor: move commitlint config to package.json

* 1.11.1
  • Loading branch information
sapachev authored Nov 22, 2024
1 parent 115157d commit 200282d
Show file tree
Hide file tree
Showing 8 changed files with 15 additions and 38 deletions.
3 changes: 3 additions & 0 deletions .git-hooks/commit-msg
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
#!/bin/sh

npx --no -- commitlint --edit $1
3 changes: 3 additions & 0 deletions .git-hooks/pre-commit
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
#!/bin/sh

npx pretty-quick --staged
4 changes: 0 additions & 4 deletions .husky/commit-msg

This file was deleted.

4 changes: 0 additions & 4 deletions .husky/pre-commit

This file was deleted.

2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ The main configuration is stored in the `config.json` file located in the root d
}
```

It is possible to run a hot-reload server to develop your own theme with custom markup, styles, and scripts. To start the development server, simply run the command `npm run dev`. This command will launch the server on 8080 port: ([http://localhost:8080](http://localhost:8080)). By default, this address will be opened with a first status code defined in the `src` directory, which corresponds to the configured `locale` value. You can choose any other code to continue developing a specific page. Don't be surprised by the injected code segments in a rendered page, as this is a feature of hot-reload mode. Any modifications to the main configuration will require a restart of the development server. During development, only the configured theme and locale directories are beign monitored.
It is possible to run a hot-reload server to develop your own theme with custom markup, styles, and scripts. To start the development server, simply run the command `npm run dev`. This command will launch the local server on 8080 port ([http://localhost:8080](http://localhost:8080)). By default, this address will be opened with a first status code defined in the `src` directory, which corresponds to the configured `locale` value. You can choose any other code to continue developing a specific page. Don't be surprised by the injected code segments in a rendered page, as this is a feature of hot-reload mode. Any modifications to the main configuration will require a restart of the development server. During development, only the configured theme and locale directories are beign monitored.


### Templates
Expand Down
3 changes: 0 additions & 3 deletions commitlint.config.js

This file was deleted.

26 changes: 2 additions & 24 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 6 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "error-pages",
"version": "1.11.0",
"version": "1.11.1",
"description": "Lightweight tool to create static HTTP Error Pages in minimalistic adaptive and accessible design with customization and localization support",
"main": "index.ts",
"scripts": {
Expand Down Expand Up @@ -41,7 +41,6 @@
"chokidar": "^3.5.3",
"coveralls": "^3.1.1",
"eslint": "^8.32.0",
"husky": "^8.0.0",
"koa": "^2.14.2",
"koa-sse-stream": "^0.2.0",
"lint-staged": "^13.1.0",
Expand All @@ -52,6 +51,11 @@
"pretty-quick": "^3.1.3",
"sinon": "^15.0.1"
},
"commitlint": {
"extends": [
"@commitlint/config-conventional"
]
},
"lint-staged": {
"**/*": "prettier --write --ignore-unknown ."
}
Expand Down

0 comments on commit 200282d

Please sign in to comment.