Yesterday was #productive. I made #progress in the new utility #app I've been working on (it's mostly for myself, but the purpose is to make #software #releasenotes creation quicker and easier. I might release it to the public some day, idk). Anyway, I'm trying to get it to wok not only cross-platform with #web, #android, and #ios (easy with #capacitor), but also have the same #codebase releasable on #desktop with #electron. I got a little #template #project going on to be able to create apps like that quicker. The #problem I ran into is the #storage mechanism for #electron. Neither #electron-store nor #electron-storage #npm #packages worked with my project for some reason. ā¹ļø I was finally able to make progresss yesterday by getting simple #json file persistence working with the electron stuff while NOT BREAKING the web stuff. š That was annoying af previously: get electron storage to work, it breaks the web stuff and vice versa.
Finally I got a #solution working, tho. š© Many hours and lots of frustration later.
After I iron it out some more, I'm going to update the #template for such projects with it. While it kight, technically, not be ideal to have storage related stuff built into a #scaffolding project for creating new apps, I think it will be more beneficial than not. Worst case scenario: whoever doesn't want it can just delete it out of the newly scaffolded project. I'll probably include instructions on how to delete it right in the readme on #GitHub
TerrestrialOrigin
npub16gā¦6gl4y
2025-02-16 15:40:36
Author Public Key
npub16ga0ftymhu7fuhz5n8sn9hf9yft42x5q2x5wg986t8m5z7ls0tds86gl4yPublished at
2025-02-16 15:40:36Event JSON
{
"id": "76381213c8fc7598db3ec585d013c48c2c0e37247afba8c0ac1a7363c1f04166",
"pubkey": "d23af4ac9bbf3c9e5c5499e132dd252257551a8051a8e414fa59f7417bf07adb",
"created_at": 1739720436,
"kind": 1,
"tags": [
[
"t",
"productive"
],
[
"t",
"progress"
],
[
"t",
"app"
],
[
"t",
"software"
],
[
"t",
"releasenotes"
],
[
"t",
"web"
],
[
"t",
"android"
],
[
"t",
"ios"
],
[
"t",
"capacitor"
],
[
"t",
"codebase"
],
[
"t",
"desktop"
],
[
"t",
"electron"
],
[
"t",
"template"
],
[
"t",
"project"
],
[
"t",
"problem"
],
[
"t",
"storage"
],
[
"t",
"electron-store"
],
[
"t",
"electron-storage"
],
[
"t",
"npm"
],
[
"t",
"packages"
],
[
"t",
"json"
],
[
"t",
"solution"
],
[
"t",
"scaffolding"
],
[
"t",
"GitHub"
],
[
"t",
"github"
]
],
"content": "Yesterday was #productive. I made #progress in the new utility #app I've been working on (it's mostly for myself, but the purpose is to make #software #releasenotes creation quicker and easier. I might release it to the public some day, idk). Anyway, I'm trying to get it to wok not only cross-platform with #web, #android, and #ios (easy with #capacitor), but also have the same #codebase releasable on #desktop with #electron. I got a little #template #project going on to be able to create apps like that quicker. The #problem I ran into is the #storage mechanism for #electron. Neither #electron-store nor #electron-storage #npm #packages worked with my project for some reason. ā¹ļø I was finally able to make progresss yesterday by getting simple #json file persistence working with the electron stuff while NOT BREAKING the web stuff. š That was annoying af previously: get electron storage to work, it breaks the web stuff and vice versa.\n\nFinally I got a #solution working, tho. š© Many hours and lots of frustration later.\n\nAfter I iron it out some more, I'm going to update the #template for such projects with it. While it kight, technically, not be ideal to have storage related stuff built into a #scaffolding project for creating new apps, I think it will be more beneficial than not. Worst case scenario: whoever doesn't want it can just delete it out of the newly scaffolded project. I'll probably include instructions on how to delete it right in the readme on #GitHub ",
"sig": "9677f1a3a2a9558da5df8fdaac4968b056f9b12cc9f7ceb441aab6e00a52c4e96113ffdf8c5aae543a368b1b73e5fa34487af1cda20f266f53e3db887505abb9"
}