Skip to content

Commit b931b4a

Browse files
committed
Remove redundant example
1 parent 3415a56 commit b931b4a

3 files changed

Lines changed: 4 additions & 11 deletions

File tree

.gitmodules

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
11
[submodule "themes/hermit-V2"]
22
path = themes/hermit-V2
33
url = https://github.com/1bl4z3r/hermit-V2
4+
[submodule "themes/archie"]
5+
path = themes/archie
6+
url = https://github.com/athul/archie

content/posts/rules.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -63,17 +63,6 @@ These rules catch the performance killers that don't show up until you're under
6363
For most applications, they're probably overkill - but if you're one of the lucky few startups with actual users, these patterns become critical.
6464
They're designed to prevent issues that work fine in development but can bring down your entire API when traffic picks up.
6565
66-
```yaml
67-
custom_rules:
68-
- name: "Avoid Blocking Operations in Request Handlers"
69-
applicable_files:
70-
- "routes/**/*.js"
71-
- "api/**/*.js"
72-
- "**/*handler*.js"
73-
description: "Don't use synchronous operations (fs.readFileSync, crypto.pbkdf2Sync) in request handlers as they block the event loop and kill performance under load. Use async alternatives or move to worker threads. One blocking operation can take down your entire API response time."
74-
```
75-
76-
7766
```yaml
7867
custom_rules:
7968
- name: "Avoid Blocking Operations in Request Handlers"

themes/archie

Submodule archie added at f2f74a5

0 commit comments

Comments
 (0)