iiinova — where your digital self keeps evolving

100% understanding. I'm slowly going that way, but some of my current workflows make that a little more challenging (bringing up a fully work environment takes about half of my M5 Pros memory/cpu resources 🤣). I also like the ability to hop in and edit/run things locally without a lot of friction.

000

doh! I should note I'm only using local host + mobile (iOS), but have plans to setup more hosts at some point.

100

welcome. I do think Paseo has a slight edge in the natural feel, but Orca isn't that far off. Let me know what you think and if it fits your workflow (the mobile app is robust as well, and generally nice, but a touch buggy on a few features like spawning a session based on a github issue)

100

Orca is not perfect for sure, especially with some quirks with Chat UI (which is experimental) and mobile rendering, but none of the aforementioned are perfect so it's all about tradeoffs. I was really happy with OpenChamber until they (re)removed claude sub support, which is a deal breaker for me.

100

bug: Support Svelte syntax highlighting · Issue #3364 · getpaseo/paseo

...edit file view (which also doesn't show what changed as green/red). In all, I have hopes Paseo will continue to improve (recently received .svelte support after someone asked 😁 - github.com/getpaseo/pas...) atm Orca feels like Paseo but 6-12 months ahead in development (very robust)

github.com

What's broken Currently all Svelte *.svelte files do not have any syntax highlighting, making it difficult to review within Paseo. File should be highlighted similar to Github (example) Steps to re...

Regarding diffs: I'm looking for an integrated view/edit per file workflow, similar to what I use in vscode (open up individual file, if I see something I want to manually write I can do so there while seeing the changes (green/red) Paseo has a single "Diff" view for all changes and an explicit...

Paseo is great and is the first to really sell me on agentic orchestration. Mostly of my issues are fairly minor, but add up. Biggest ones: 👎 Very little git control (commit message, staging individual files (or lines of files)) 👎 Similar for PR creation 👎 Reviewing diffs is suboptimal...

120

Bonuses: ✓ Integrated browser ✓ Granular diff support (last turn, commits in branch, etc) ✓ Convenient way to monitor subscription usage ✓ Streamlined flows (turn issues into investigations / PRs) ✓ Explicit subagent spawning ✓ Multiple sessions per branch/worktree

030

My requirements: ✓ Multi-vendor models (rules out claude/codex desktop) ✓ Claude + Codex subscriptions (rules out opencode / OpenChamber recently) ✓ Chat UI (not just claude/codex cli) ✓ Robust git control (not just accept commit / PR) ✓ Worktree (over container) isolation (atm) ✓ Mobile app

130

It all leverages LayerChart and LayerStack under the hood, which I’ve been building for over 5 years (before and after the AI takeover).

000

Most of my development nowadays is human-in-the-loop AI with a good bit of iteration. The initial site took about 2 weeks of iteration before it was released, and continue to add features and improvements since. A quick look at my agent history shows over 5k+ messages (across 37 sessions atm)

100

as @graphieros.npmx.social pointed out, npm data processing issues resulting in `0` download days (and never retroactively fixing) I've been making these anomalies more prominent in npmchart.com using: - dashed lines / area gaps (when daily viewed) - axis annotations (!) - tooltip explainers

170

Sean Lynch @techniq.dev · 24/09/2026

npmchart.com can now be installed as a web app 📲

060

there's no way I could find to pull npm dependents via an API (or scraping) so just provided a link, but Github repos and packages provide good coverage. from my understanding Github includes these if a repo/package ever referenced them, but npm only lists it if it is still active.

001

Sean Lynch @techniq.dev · 24/09/2026

how about something like...

200

@hayleigh.dev Let me know if you have any suggestions on what would be most useful for you

100

These could be REALLY large values, and also interesting to see large differences between Github (which has repos & packages) and npm github.com/sveltejs/sve... www.npmjs.com/package/svel... Will take some thought on what provides some useful insights (and accurate) and availability via API

000

Composable Svelte chart components to build a large variety of visualizations

Interesting... Should be possible, both from a dependent package, but also repo perspective. The later I use to build LayerChart's showcase page: www.layerchart.com/docs/showcase

layerchart.com

LayerChart

210

pngwn @pngwn.at · 22/09/2026

Improvements on the dependencies drilldown: ✓ Table view with grouping / sorting ✓ Sankey view ✓ Horizontal partition view (vertical / flamegraph available as toggle) ✓ Improved data fetching ✓ more UI polish Let me know how else we can improve this 🤔

140

Reposted by Sean Lynch

After about a year, on and off, I am veeeery happy to release TWINKLEPLOP, a syntax highlighter of tremendous power! The speed of prism with the customisation of Shiki. twinkleplop.pngwn.at

519233

We've also added a lot of polish since the initial release: ✓ missing download day annotations ✓ version selection (useful for dep analysis) ✓ flip-transitioned tooltip items (useful when they change order) ✓ further refine npm API usage to reduce rate limiting ✓ show more user avatars

010

Flamegraph (Icicle) view Same install analysis as Treemap but using a single dimension (length instead of area) which can make direct comparison easier but less efficient with viewport real estate. Also supports zoom drilldown.

Sunburst view Same install analysis as Treemap but radially, for people who like circles at the sake of comparison. Also supports zoom drilldown.

Treemap view Useful to analyze install sizes and includes drilldown zooming by clicking on a group, or package details.

Graph view supports pan/zooming, hover to highlight upstream/downstream dependencies, click to load more per node (or depth), and package drilldown details.

📦 npmchart.com: dependency analysis Analyze package dependencies as a graph, treemap, sunburst, or flamegraph including how each dependency affects install size

1143

first framework problems 🤣

090

I personally haven't used columnar data much thus far, but feel like any day now that use case will make itself present.

000

Interesting... I need to look closer into this as well for LayerChart at some point. We try to support a variety of data shapes (but all POJOs at the end of the day): www.layerchart.com/docs/guides/... and have a few examples to see how each perform: www.layerchart.com/docs/example...

layerchart.com

Download trends, releases, and repository activity for any npm package

Thanks, and npmchart.com is very much a complement to @npmx.dev. Svelte needs more public projects to showcase. I have plans for more 😁

npmchart.com

npmchart

030

React (shots fired!)

100

Reposted by Sean Lynch

Provide repo / package overview · Issue #16 · techniq/github-analysis

Thanks, and 100%! (and should have called it out) npmchart.com is a re-envisioning of another project (github.techniq.dev), but oss-analytics was the strongest inspiration for it's insights, but work for any package (and github repo), more dynamic (drilldowns, link outs, etc), compare, etc

github.com

021

Provide repo / package overview · Issue #16 · techniq/github-analysis

github.com

021

Upvote ratio is currently 91.7% so have some people to win over (but that's Reddit)

000

Sean Lynch @techniq.dev · 16/09/2026

🏆 Top of r/sveltejs today www.reddit.com/r/sveltejs/

1140

Thanks! Let us know how we can make it better.

010

Sean Lynch @techniq.dev · 16/09/2026

Thanks! Sadly there doesn’t appear to be any way to increase rate limiting with NPM (unlike GitHub) via auth/token. Most of the loading is done client-side to isolate rate limiting to per-user, but it’s still very tight. I have a few server-side data fetches with caching I plan to replace soon.

210

Sean Lynch @techniq.dev · 16/09/2026

Glad you like it! Let me know how we can make it better.