Skip to content

Commit ba7a020

Browse files
committed
edits
1 parent 5a58b2f commit ba7a020

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/blog/directives-the-new-framework-lock-in.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,14 @@
11
---
2-
title: Directives Are Becoming the New Framework Lock In - A Quiet Problem in the JavaScript Ecosystem
2+
title: Directives Are Becoming the New Framework Lock In
33
published: 2025-10-24
44
authors:
55
- Tanner Linsley
66
---
77

88
![Directives Are Becoming the New Framework Lock In - A Quiet Problem in the JavaScript Ecosystem](/blog-assets/directives-the-new-framework-lock-in/header.png)
99

10+
## A Quiet Problem in the JavaScript Ecosystem
11+
1012
For years, JavaScript has had exactly one meaningful directive, `"use strict"`. It is standardized, enforced by runtimes, and behaves the same in every environment. It represents a clear contract between the language, the engines, and developers.
1113

1214
But now we are watching a new trend emerge. Frameworks are inventing their own top level directives, `use client`, `use server`, `use cache`, `use workflow`, and more are appearing across the ecosystem. They look like language features. They sit where real language features sit. They affect how code is interpreted, bundled, and executed.

0 commit comments

Comments
 (0)