Reactive analysis blog. #1163
Reactive analysis blog. #1163
Conversation
Deploying rescript-lang-org with
|
| Latest commit: |
7929f1a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://908d62d1.rescript-lang.pages.dev |
| Branch Preview URL: | https://reactive.rescript-lang.pages.dev |
cristianoc
force-pushed
the
reactive
branch
2 times, most recently
from
6aad775 to
8463b58
Compare
cristianoc
force-pushed
the
reactive
branch
3 times, most recently
from
943da9a to
fe19237
Compare
Add reactive-analysis.mdx and align metadata with blog conventions (author/date, links).
…structions - Add monorepo support bullet point under "For Developers" - Rewrite "Try It Today" section with version requirements and simple editor workflow - Add link to Dead Code Analysis documentation Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The reactive analysis blog post references SVG diagrams via absolute paths (/blog/reactive-analysis/*.svg). The link validator resolves these relative to the markdown file and reports them as missing. Check whether warned-about files exist in public/ before reporting, since Vite serves public/ assets at root. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Cloudflare deploymentDeployement ID: 3167954f-fd63-4019-aab7-a980324787e1 ⛅️ wrangler 4.63.0 ✨ Uploading _redirects |
zth
left a comment
zth
left a comment
There was a problem hiding this comment.
I love this post, so much fun to read something fairly in depth! Great work.
I had one small comment, and then a general note - given the shift towards more agentic coding, it might be worth to add a section about that this will also greatly benefit agents in that you can get a super fast and tight feedback loop for them (which means they could clean up your codebase, etc).
| Imagine editing a ReScript file and seeing dead code warnings update almost immediately as you work. No waiting for a full re-analysis command. Just continuous feedback about which parts of your code are actually used. | ||
|
|
||
| This is what we're bringing to ReScript. | ||
|
|
||
| The static analyzer that powers dead code detection is being rebuilt on a **reactive foundation**. When you add a reference to a function, the "unused" warning vanishes quickly. When you remove the last use of a module, the dead code warning appears right away. The analysis stays in sync with your code, updating in real time. |
There was a problem hiding this comment.
I think it's worth adding that it's "project wide dead code warnings". Other tools (eslint etc) has plenty of dead code warnings etc for the current file. But this is for the entire project, something that is notoriously bad/slow in most solutions.
3 participants
No description provided.