eslint-plugin-use-agnostic 0.6.0 → 0.6.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -109,7 +109,7 @@ But not having a directive to distinguish between 1. non-special Server Modules
|
|
|
109
109
|
|
|
110
110
|
- Developers are confused and have no idea what "Server" or "Client" means, since React doesn't make it crystal clear.
|
|
111
111
|
- LLMs are confused, because even they can't understand what 'use server' and 'use client' mean and therefore cannot explain it to developers facing their own specific concerns.
|
|
112
|
-
-
|
|
112
|
+
- And if LLMs are confused, I can't even imagine what that must mean for AI tools and AI agents.
|
|
113
113
|
|
|
114
114
|
This is what the 'use agnostic' directive solves. It clearly marks a module to be an Agnostic Module. And if a module that used to lack a directive can now be marked as an Agnostic Module, this allows modules without a directive to finally, truly be Server Modules by default. And eslint-plugin-use-agnostic can work from there.
|
|
115
115
|
|