electron-quick-start VS trpc

"pack": "build --dir","dist": "build","electron": "electron main.js","postinstall": "install-app-deps" Create main.js I just copied the code from the electron quick start. The only change I make is to the location of index.html which I set to /dist/index.html

Tauri has a small footprint by default but what about when we pack NodeJS binary with our app? The result of this is surprising. Taurine app is 3 times smaller than electron app. Compiled the Tauri app in .app the format has 63MB and the electron app in the same format has 205MB.

I cloned the quick-start directory from Electron's github and spun up my node-js. No problems there. 🦾

Well it automatically downloads electron 19.0.4 from git clone https://github.com/electron/electron-quick-start. Then I instantly receive the vulnerability issues from npm install & npm start. Not sure why the packages aren't upgrading to newest on install

# Clone this repository git clone https://github.com/electron/electron-quick-start # Go into the repository cd electron-quick-start # Install dependencies npm install # Run the app npm start

This was like one of the top results when I googled for like "electron stuck npm" https://github.com/electron/electron-quick-start/issues/127

This question already has answers here: How to deploy an Electron app as an executable or installable in Windows? (10 answers) Closed 2 years ago.I've been learning how to create applications in Electron and I need help compiling a simple project to a Windows executable. The program is a clone from this Github repo: https://github.com/electron/electron-quick-start. On the repo readme it shows how to run the program:

Create an electron application. Follow the steps here: https://github.com/electron/electron-quick-start

In any event, I just took a closer look at my project, and it looks like the key thing is to wait for Electron's ready event before registering the ipcMain listeners. So, taking Electron's quick-start example as a starting point, you would want to do it in the app.whenReady().then(() => { ... }) callback, probably just before creating the window. Does that help?

We will first initialise an empty electron project that will look similar to an electron first app or electron quick starter repository

RESTful API: RESTful API does not have machine-readable metadata cacheable, and query validation is not available.(There are some libraraies tried to solve this issue like TRPC)

tRPC + Cloudflare Workers Example

Hi I'm working with trpc + nextjs app dir (unsupported by trpc currently) and trpc context

I'm using TRPC with Next13 App directory and I can't manage to invalidate queries. Seing from their example there is a way to do it https://github.com/trpc/trpc/blob/96956e790e6862bcc6dcc4622edc8e48da0adbcb/examples/.experimental/next-app-dir/src/app/post-example/page.tsx

It is. But RSC make many library authors and maintainers question whether their library is still needed in a RSC world and if so how they can support it. Same story with tRPC https://github.com/trpc/trpc/issues/3297

Also, while trying to debug this, and this is way outside my league but I noticed this: Is there possibly an error in the Updater TS-definitions in https://github.com/trpc/trpc/blob/main/packages/react-query/src/shared/proxy/utilsProxy.ts at lines 155+156 & 167+168 because they are duplicate-lines and seems to be where my issues are coming from.

Unfortunately, tRPC and NestJs do not play well together by default, and the tRPC team does not intend to integrate the two through an official plugin for the time being.

- https://github.com/trpc/trpc: End-to-end typesafe APIs made easy. Never write another API contract again.