I've found the memory limits to block more of my projects than cpu time. They seem to send multiple requests to a single node/process and if you're making some sort of remix app it easily breaks with any kind of load.

The other thing i've noticed about burritos is that more places take card or apple pay now. When I moved to sf in 2015 many of them were cash only, same with bars. I always assumed some amount of cash was being shuffled under the table.

And when you take cards or things like tap to pay, you pay higher rates as a biz which gets factored into overall prices. But...good luck being cash only in a lot of places.

I still carry cash because services like massage and housecleaning and some restaurants are happy to give good price breaks for cash payment, but I also love Apple Pay as a consumer.

run your backend tests against this in memory and tests can be run in parallel instead of using a single real postgres instance

Our HoA uses google groups. Mild spam, but overall pretty good for threads. Too many people spam everyone asking for a plumber or whatever

What are you doing that requires checking in the compiled version. Esbuild takes like one second

The code is written in typescript. So we go from

    * cloning the action 
    * running the dist/index.js

to

    * Cloning the action
    * npm install
    * npm compile
    * npm run

You can run TypeScript natively in Node.js 24, actions based on that runtime don’t need a build step.

https://bsky.app/profile/danielroe.dev/post/3lxczp5apec2x

I think it just ignores types, so may not suit all use cases.

It has a (albeit experimental) flag for transforming enums, namespaces and other runtime-impacting aspects of TypeScript, if that’s what you were referring to?

https://nodejs.org/api/cli.html#--experimental-transform-typ...

That's fair, I'm referring to the number of mistakes that happen with local publishing. Publishing the wrong branch, not building from latest etc

So add a wrapper for that, a quick script that checks which branch and revision you are publishing from. The issue here is publishing from a CI you do not control that well and with automated events.

You can run the exact same script locally as you do in CI, with the only difference being the addition of a 2FA prompt.

That's a good point, I would lose package provenance that way. I guess that is fine since it didn't prevent anything here.

I can look into that.

Sorry if that wasn't clear. This was a token with global publish rights to my npm packages.

I was confused too. Was it your npm token stored in angulartics2 as a Github Actions secret, so it could publish new angulartics2 versions?

Yes, exactly.

there's existing libraries in this space that are quite good. not sure why you would use this instead.

storage for example:

https://github.com/unjs/unstorage vs byojs storage https://github.com/byojs/storage

most users are going to prefer autocomplete and types regardless of if they also use typescript.

esbuild can bundle typescript files directly, you don't need tsc to strip types

edit: nevermind i get what you're saying. check types with tsc and dev work with esbuild