freenatec

If you’re using WSL 2, but your project files are in windows-land and vscode is reading them via the mnt path (like /mnt/c/code/myproject), then you’re going to have show-stopping performance problems.

I’ve found code generation tools extremely helpful for large-ish graphql backends and resolve many of the ‘complexity’ issues if employed correctly.

Of course, code generation has its own particular set of gotchas and problems (for example, you really don’t want to expose the full functionality of, say, the Prisma api to the world)

I started developing an electron app earlier this year and after trying all the available boilerplates and clis I ended up with an app based off nextjs electron-typescript example which uses electron-builder that I’m very happy with. (Nextron is a cool project but is more than I needed)

The major pain point with the existing clis/boilerplates was building the app for multiple platforms in a container and then running automated tests using Playwright, and also being able to run those tests locally if I wanted to, without needing to do any futzing with configuration between environments, and also having basic dev perks like reloading on src code changes and nextjs bundling when building prod.

Also, it’s hard to overstate how nice it is to just not have to deal with webpack configuration.

One would assume that absence of credentials would necessarily = auth failure.

Like, the basic flow would check the validity and, implicitly, the presence of the auth header. To bypass auth in the case of the absence of the header itself would need to be an explicit conditional. IF no header, then authenticated. Right? That’s crazy.

I suppose I could look at the code.