silverwind

Yes, tsconfig is a mess to scope. It needs a re-design to allow glob-based matching for all options and in typescript instead of jsonc.

Seems they not running these agents with the same permissions of the user prompting them, what a disaster.

I think tsdown is much better suited for CLI and library builds. Vite has many web-isms that don't matter for these.

Yeah, a missed opportunity. But I'm sure such a compiler will eventually arise.

True, sometimes a Claude answer is so on the spot, it'd a waste to not post it alongside your short summary.

PR spam is a major problems for repo that run bounties. Maybe GitHub should temporarily block accounts from raising PRs if like 95%+ of them are getting rejected.

Knowing them, I expect a release probably next week, have fun in production with it.

It'll always be a cat-and-mouse game. If npm adds protections, it'll only yield false-positives and workarounds will be trivial.

Almost all these recent compromises seem to involve either cache poisoning or prompt injection via untrusted variables.

Python had these too, no ecosystem is safe.

I think it's just a case of brain drain, followed by reckless AI adoption which both drove the quality down.

All those forks turned out to be inferior projects with substantially less contributions than the originals.

It's definitely helpful to know whether a PR was AI-assisted or not and the git attribution line is a simple and effective way of communicating that.

I also recommend specifying model name and version so the maintainer knows upfront the level of slop they are dealing with.

I'm going even simpler, just bare docker with a idempotent bash wrapper.

I hope Node eventually gets a WebSocket server like Bun has.

Problem with Go is the type system is rudimentary, so you can't "restrict" AIs as well as you could in Typescript.

https://www.typescriptlang.org/tsconfig/#erasableSyntaxOnly covers them all, I strongly recommend running with that option enabled to be future-proof.

Modern Typescript does not need runtime features.

Maybe now people can stop blaming npm and realize none of these unreviewed package ecosystem are safe.

Could that be the explanation for the recently increased token use?

Slopilot

This seems nonsensical. Why would non-actions activity consume actions budget?

TLDR: It's a 6-9x price increase

Use `background-color` in Firefox's `userContent.css`.

Still worth it imho for important code, but it shows that they are hitting a ceiling while trying to improve the model which they try to solve by making it more token-inefficient.

/effort is only per-session though, not persistent.

Slow is good thought, that's when you know it'll get it right.

Seems so silly that they won't support `effortLevel: "max"` while a env var is perfectly fine.

This needs to be supported on `git` level first imho, not by a forge vendor.

`git diff` is probably all you need.