@dobbel thanks for the reply and sorry for the late response.
your solution works on paper but the tick strategy is lost, :ticked.sync is also lost - both important things to reduce code. cleanest way would be to somehow resolve the bug only by props or something
@mosiki You should not try to require index.js from src-ssr after build, as that file must be processed by quasar cli. You could try adding firebase functions in another file in src-ssr and require that, but I’m not familiar with firebase.
Think of it this way though, anything in src-ssr is the source files for an express sever. Once you build, the express server gets built to the dist dir and is independent of quasar at that point. Usually to deploy you just copy the dist dir to the server, yarn install, and run.
@operez2000 The express server under src-ssr does not run with Electron. You would have to re-create the express api under src-electron. You could share code between the two and require the shared code in both src-ssr and src-electron. But it’s not always the best idea to run a server locally this way, depending on your security model since the endpoint is completely exposed to any process running on that user’s computer. Also, the user might be running something else on that port (which can be solved by using a randomized port on start.)
But better yet is to use electron’s ipc to communicate from the frontend to the backend. It would require some more work to make the frontend either call ipcRenderer or axios depending on the mode. You still could share code between ssr and electron, but it involves more work.
Ah, forgot the ginger and Apple. And I also add one Jalapeno pepper and fresh garlic with the mix. 🙂
Gets real spicy. That’s actually counts as one meal, and I eat a normal lunch as my second meal.
@iamtetea if you understood the code, content is just the data array converted into string delimited by commas, you can do whatever with it just follow the correct pattern for it to be a valid csv format.