Generally in next.js it's best practice to store authentication tokens in cookies so that the token can be read in both the server and client for SSR (e.g. in getInitialProps). Since electron doesn't support cookies in the renderer process - what would be the best way to keep track of auth tokens (and persist them between sessions)?
In now-desktop, it seems like a config in the main process is used and then electron remote is used to communicate with the config. Is there a more simple best practice than this?
Generally in next.js it's best practice to store authentication tokens in cookies so that the token can be read in both the server and client for SSR (e.g. in getInitialProps). Since electron doesn't support cookies in the renderer process - what would be the best way to keep track of auth tokens (and persist them between sessions)?
In now-desktop, it seems like a config in the main process is used and then electron remote is used to communicate with the config. Is there a more simple best practice than this?