next-pwa VS syncthing-android

/** @type {import('next').NextConfig} */ const path = require("path"); const isDev = process.env.NODE_ENV !== "production"; const withPWA = require("next-pwa")({ dest: "public", disable: isDev, buildExcludes: ["app-build-manifest.json"], }); const generateAppDirEntry = (entry) => { const packagePath = require.resolve("next-pwa"); const packageDirectory = path.dirname(packagePath); const registerJs = path.join(packageDirectory, "register.js"); return entry().then((entries) => { // Register SW on App directory, solution: https://github.com/shadowwalker/next-pwa/pull/427 if (entries["main-app"] && !entries["main-app"].includes(registerJs)) { if (Array.isArray(entries["main-app"])) { entries["main-app"].unshift(registerJs); } else if (typeof entries["main-app"] === "string") { entries["main-app"] = [registerJs, entries["main-app"]]; } } return entries; }); }; const nextConfig = { experimental: { appDir: true, }, reactStrictMode: true, webpack(config) { if( !isDev ){ const entry = generateAppDirEntry(config.entry); config.entry = () => entry; } return config; }, }; module.exports = withPWA(nextConfig);

Thank you for trying it and asking questions. Let me reply to them below.

> Could you give a brief overview of how the project is built, or what libraries are used? I found two in the source, React and Workbox. I've never heard of Workbox before, and I'm still figuring out how service workers are used. But it seems like a big part of the source.

For building, I used Next.js with static generation, not using Server-side rendering. But it's not an important part because it doesn't rely on Next.js features so much.

About Workbox, the app uses them with next-pwa (https://github.com/shadowwalker/next-pwa) for providing caching strategies and offline behavior as Progressive Web App. For example, the app registers several precached files via Workbox. Precached files are fetched and cached by the service worker and these caches can be used while offline. Also, Workbox can configure runtime caching strategies. You can see details in Workbox documentation (https://developer.chrome.com/docs/workbox/).

The app also uses the Service Worker to connect IndexedDB as a local database and send HTTP requests to synchronize data with Google Drive. By using the Service Worker, these methods don't block the user interaction from the main thread and Service Worker can run in the background to synchronize data even if the browser window is suddenly closed.

We tried to use next-offline and next-pwa, but we were only able to precache the static assets.

It's possible that next-pwa might support precaching pages in the future. Subscribe to issue 252 to keep up to date on that.

I am currently using the opt-in integration for the CRA pwa. I kind of wanted to test out migrating to Next. I know NextJs has a pwa plugin. Does anyone have any experience migrating with this in mind (from cra to next)?

There's next-offline and next-pwa (and some comparison too). But has anyone here made a PWA with NextJS? Now I am not only referring to service workers/offline functionality, but also icons, adding to homescreen, manifest, and other PWA features. Does anyone have any good examples or guides to refer to?

next-pwa, for PWA support.

shadowwalker/next-pwa#132 improves error messages

We use syncthing to share files between our machines. It avoids is having to use dropbox / OneDrive etc. You just choose a folder and it automatically syncs it in the background.

https://syncthing.net/

This very hn entries is bust contradicting your statement.

Also what about syncthing[1] (for recurrent/permanent sync) and croc[2] (for one time copies) ?

I have used both for a number of years already.

[1] https://syncthing.net/

[2] https://github.com/schollz/croc

I would use syncthing, which is open source at https://syncthing.net/.

After minimal setup, it just works(tm).

You have a normal directory in your filesystem, that is synced to the other peers (which you set up in the "minimal setup").

I have been using it for years, and it works well. It has no problems crossing os'es (i.e. windows -> linux, linux -> mac)

For windows I usually recommend https://github.com/canton7/SyncTrayzor, but vanilla syncthing works fine too (but don't try to mix them!)

Do consider Syncthing particularly if you are using Android. If using apple iOS you'd need the möbius sync client.

https://syncthing.net/

https://www.mobiussync.com/

One thing that it beats the cloud / centralized sync on is because the connection is direct between devices when the initial transfer is completed the file is completely there on the other device. With a cloud type of sync you do the transfer twice. I've seen stack up on large media or with the structure of cloud services pricing making it expensive depending on how your workflow is setup with inside and outside parties. For example, Dropbox deduction from all parties' storage limits not just the sharer.

You can also point Syncthing at a local sync of Dropbox or Google drive and then forward the files to other recipients from that for some purposes.

I think sync is a non-feature, as you can just ride on your existing solution.

For example, I use syncthing [1] with Obsidian to sync files off-cloud.

https://syncthing.net/

When I was 14 and just getting started, I used Notepad. Upgraded to Wordpad when I realized I loved putting italics in every other sentence, moved to Google Docs at around 25 when I started writing on my phone and wanted to sync with my computer, finally moved to Obsidian a few months ago (with Syncthing for syncing) when I decided I don't want to live in Google's house where they can burn my stuff down whenever they want.

Pick it up again an use cloud syncing this time! Is worth! https://syncthing.net/