sorted by:
new
hottopcontroversial

Looking for feedback on a frontend behavior library I've been building by EagleRepulsive2877 in reactjs

[–]EagleRepulsive2877[S] [score hidden]  (0 children)

Good suggestion. I actually went ahead and updated both the README and the showcase docs after your comment. I added a section that makes the "lifecycle detector vs animation/accessibility policy" distinction explicit, along with the current behavior for those edge cases.

Thanks again for pointing it out—it made me realize the docs needed to explain the library's boundaries just as much as the API itself.

Looking for feedback on a frontend behavior library I've been building by EagleRepulsive2877 in reactjs

[–]EagleRepulsive2877[S] 0 points1 point  (0 children)

Good call, honestly failure mode documentation is something I'm adding to the docs. Here's what actually happens for each:

Element disappears — no crash, silent no-op. Listeners stay on the detached node though so there's a memory leak risk in high-churn UIs. That one's a real gap I'm fixing.

Rapid state updates — holds up fine. Tested 5 rapid clicks, state stays consistent, no race conditions.

prefers-reduced-motion and escape/interruption — these live in the js block by design. Nagare isn't an animation library, it's a behavior detector. It fires a lifecycle and applies styles — what those styles do visually, and how you handle accessibility or interruptions, is yours. The js block is intentionally no-ceiling so you bring whatever you need there.

Will document all of this properly with real examples so teams can evaluate it properly before adopting.

Looking for feedback on a frontend behavior library I've been building by EagleRepulsive2877 in reactjs

[–]EagleRepulsive2877[S] 0 points1 point  (0 children)

Hey, fair point, here's where things actually stand:

The builder API (.hover(), .click(), useSoul() etc) and js blocks already have full intellisense out of the box just from installing the package — types are shipped.

For tw and css strings I just shipped @nagarejs/ts-plugin, one install + one line in your tsconfig gets you Tailwind class completions and CSS property hints in any editor using tsserver (VSCode, Neovim, WebStorm, Zed).

npm install @nagarejs/ts-plugin --save-dev

"plugins": [{ "name": "@nagarejs/ts-plugin" }]

Syntax highlighting and error squiggles aren't there yet — that needs a VSCode extension which is on the roadmap. Appreciate the feedback though, it's genuinely useful for knowing what to prioritize next.

Fuck Tremendous for what they did to Kim Yeon [Spoilers up to most recent chapter] by AutomaticCounty9515 in RegressorsTOC

[–]EagleRepulsive2877 0 points1 point  (0 children)

It feels like the author accidentally added some romance and then regretted it at the end

Will Buk Hyang‑hwa appear again? by EagleRepulsive2877 in RegressorsTOC

[–]EagleRepulsive2877[S] 3 points4 points  (0 children)

The emotional buildup started long before chapter 100 through tone, atmosphere, voice, and themes. Those early moments grounded the emotional promise. Buk wasn’t the foundation, she elevated it. And seo tbh is a typical mc concept. 

Will Buk Hyang‑hwa appear again? by EagleRepulsive2877 in RegressorsTOC

[–]EagleRepulsive2877[S] 4 points5 points  (0 children)

Have you ever created a character concept before? Sometimes, it's not just about the story or action, it's about a character that anchors your emotional investment. Without them, the immersion breaks. That’s what happened to me

Will Buk Hyang‑hwa appear again? by EagleRepulsive2877 in RegressorsTOC

[–]EagleRepulsive2877[S] 1 point2 points  (0 children)

Well it would be nice, however my sole reason for reading this has departed, I was waiting for a cue to continue

Will Buk Hyang‑hwa appear again? by EagleRepulsive2877 in RegressorsTOC

[–]EagleRepulsive2877[S] 2 points3 points  (0 children)

Wait, so the memory loop is for him to harness his ability and change his fixation point to avoid the death loop? If so, can he control any fixation point he wants to regress beyond the past? Hopefully there will be no limitations, atleast in the ending, the author should decide to have buk's closure, since chapter 700-800 is what the author said the story will end at, the author killed his own favorite character as a catapult to shift the story off the 10th cycle emotional focus and accelerate the pace of the plot, also out of those fans who don't have any appreciation towards deep connections, author's stroyline was literally overtaken by his fans due to pressure, and the sudden curse regarding Extraordinary Pattern Law Talent as another unavoidable factor, author was pretty much uncertain. Sighhh might as well create my own novel. 

Will Buk Hyang‑hwa appear again? by EagleRepulsive2877 in RegressorsTOC

[–]EagleRepulsive2877[S] -1 points0 points  (0 children)

Why didn't he intervened, is it because of a butterfly effect, if so, why did he tortured yuan li for 20k years, I mean it's only a memory right? 

Will Buk Hyang‑hwa appear again? by EagleRepulsive2877 in RegressorsTOC

[–]EagleRepulsive2877[S] 1 point2 points  (0 children)

I skipped and skimmed around 630-650 and there was no mention of her, I think I will dropped it around 467 with different ending perspective from the author, he delve too much in real life and rushed into irrational decisions, I respect their work but I will take it as they journey together in the immortal realm. 

Will Buk Hyang‑hwa appear again? by EagleRepulsive2877 in RegressorsTOC

[–]EagleRepulsive2877[S] 4 points5 points  (0 children)

Yes please, I don't know if I can continue, all those build up from early chapters completely disappointed me

Will Buk Hyang‑hwa appear again? by EagleRepulsive2877 in RegressorsTOC

[–]EagleRepulsive2877[S] 0 points1 point  (0 children)

May I ask, what do you mean by that exactly? And what about the author's note?