next-pwa
rehype
Our great sponsors
next-pwa | rehype | |
---|---|---|
9 | 17 | |
3,592 | 1,619 | |
- | 3.4% | |
2.4 | 6.6 | |
3 months ago | 2 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
rehype
-
I built an Markdown editor using Next.js and TailwindCss 🔥
Add Remark and Rehype plugins
-
Building an Astro Blog with View Transitions
Astro content collection are as simple as a folder containing a bunch of Markdown (or Markdoc or MDX) files if that's the only thing you need, but they can also do relationship matching between different collections, frontmatter validation using zod and you can also customize how the markdown is parsed and translated to html using rehype and remark and their plugin ecosystem.
- Example of Powerful Markdown Editor combining Svelte-Exmarkdown and Skeleton
-
How to integrate your blog with dev.to API Next.js 13
That's all to render the post as HTML, there are lots of things you can do to customize the results, you can check the remark plugins and rehype plugins to pass as props to and you can also take a look at some other bloggers if you're looking for different styles for example Lee Robinson's or if you liked mine.
-
Serving Docusaurus images with Cloudinary
Now we have our Cloudinary account set up, we can use it with Docusaurus. To do so, we need to create a rehype plugin. This is a plugin for the rehype HTML processor. It's a plugin that will transform the HTML image syntax into a Cloudinary URL.
-
Contentlayer with next/image
The next idea was to use normal markdown images and to place the images in the public folder. This eliminates the need for static import and treats our image like a remote image. But in order to make this work, we have to tell next/image the dimensions of the image. If we would use a static import for the image, the import magic would provide the dimensions for us. To pass the width and height to the image component we use a rehype plugin called rehype-img-size.
-
Creating a blog with Astro and MDX
Astro makes it easy to add Remark or Rehype plugins to your markdown. You can extend add a markdown property to the Astro config file, an add a function/plugin to the remarkPlugins property (the extendDefaultPlugins property is added to make sure the default plugins aren't overwritten by this config change):
-
Converting and customizing Markdown files to HTML with Unified, remark & rehype
rehype: "rehype is a tool that transforms HTML with plugins. These plugins can inspect and change the HTML. You can use rehype on the server, the client, CLIs, deno, etc."
-
Render Markdown from a string in Svelte (mdsvex / SvelteKit)
This means that you can transform your HTML with tools like rehype or remark. You can find out more about the available options here.
-
Building React Components from headless CMS markdown
The HTML syntax tree is transformed through rehype, and rendered to React components.
What are some alternatives?
next-offline - make your Next.js application work offline using service workers via Google's workbox
remark - markdown processor powered by plugins part of the @unifiedjs collective
next-seo - Next SEO is a plug in that makes managing your SEO easier in Next.js projects.
next-mdx-remote - Load mdx content from anywhere through getStaticProps in next.js
Next.js - The React Framework
rehype-toc - A rehype plugin that adds a table of contents (TOC) to the page
sqlite-worker - A simple, and persistent, SQLite database for Web and Workers.
remark-directive - remark plugin to support directives
Sentry-Picam - A simple wildlife camera for Raspberry Pis.
remark-extended-table - remark plugin to support table syntax allowing colspan / rowspan
prism-react-renderer - 🖌️ Renders highlighted Prism output to React (+ theming & vendored Prism)