next-pwa
nanoid
Our great sponsors
next-pwa | nanoid | |
---|---|---|
9 | 83 | |
3,602 | 23,187 | |
- | - | |
2.4 | 8.3 | |
3 months ago | 22 days ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
next-pwa
-
Enable PWA with next.js 13 or later using next-pwa (disabled in development environment)
/** @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);
-
Show HN: Duck, a chat-based note app for your knowledge base
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.
-
PWA support in NextJs
We tried to use next-offline and next-pwa, but we were only able to precache the static assets.
-
Precaching pages with next-pwa
It's possible that next-pwa might support precaching pages in the future. Subscribe to issue 252 to keep up to date on that.
-
Question about Nextjs and CRA PWA
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)?
-
Does anyone have any experience with making PWAs in 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?
-
I over-engineered my blog, and here’s what I’ve learned
next-pwa, for PWA support.
-
tmp.spacet.me devlog part 1
shadowwalker/next-pwa#132 improves error messages
nanoid
-
Next.js and Bunny CDN: Complete Guide to Image Uploading with Server Actions
Last thing left is to use our new upload function in our server action. Since I like to upload images in single format and have some more control over them, I will additionally use sharp library. For file name, I'll generate some random string using nanoid:
- Nano ID Collision Calculator
-
Why we chose Bun
Our API is in node. And God, how I suffered to import nanoid in an esmodule project. I had to vendor it, since using a previous version was not ideal. With bun, we can no longer worry about that. Just import what you need and done.
-
UUIDv7 is coming in PostgreSQL 17
No thread about UUID is complete without a plug for NanoID! https://github.com/ai/nanoid/blob/main/README.md
-
Building a File Storage With Next.js, PostgreSQL, and Minio S3
Generate a unique file name using the nanoid library.
-
Building a Multi-Tenant App with FastAPI, SQLModel, and PropelAuth
The syntax should read similar to SQL itself. We’re using a Python port of nanoid to generate our IDs. There’s only one thing missing… how do we actually create the table?
-
You Don't Need UUID
I usually go for Nano Id for new projects https://github.com/ai/nanoid
-
Enhance Your Web Apps: Best JS Libraries 🔧
Nano ID
-
Analyzing New Unique Identifier Formats (UUIDv6, UUIDv7, and UUIDv8) (2022)
In another comment I mentioned I use nanoid in my projects now. It has a default space of 64^21 and has an a page where you can play with key lengths and alphabet sizes and see the probability of collisions :
https://zelark.github.io/nano-id-cc/
At the default 64 character alphabet with a 21 character key length it would take ~41 million years in order to have a 1% probability of at least one collision if you generated 1000 ids per second.
-
How I use Nano ID in Rails
Using randomly generated IDs like Nano ID could be a good alternative, however, as a developer, we must understand what Nano ID really does in our application. Defining the number of characters in the generated IDs is also important, to help with that Nano ID has a Collision Calculator to give us how many years in order to have a 1% probability of collision.
What are some alternatives?
next-offline - make your Next.js application work offline using service workers via Google's workbox
snowflake - Snowflake is a network service for generating unique ID numbers at high scale with some simple guarantees.
next-seo - Next SEO is a plug in that makes managing your SEO easier in Next.js projects.
ksuid - K-Sortable Globally Unique IDs
Next.js - The React Framework
typedorm - Strongly typed ORM for DynamoDB - Built with the single-table-design pattern in mind.
sqlite-worker - A simple, and persistent, SQLite database for Web and Workers.
pg_random_id - Provides pseudo-random IDs in Postgresql databases
Sentry-Picam - A simple wildlife camera for Raspberry Pis.
jest - Delightful JavaScript Testing.
next-mdx-remote - Load mdx content from anywhere through getStaticProps in next.js
Numeral-js - A javascript library for formatting and manipulating numbers.