next-pwa
next-mdx-remote
Our great sponsors
next-pwa | next-mdx-remote | |
---|---|---|
9 | 20 | |
3,592 | 2,386 | |
- | 4.3% | |
2.4 | 5.2 | |
3 months ago | about 1 month ago | |
JavaScript | TypeScript | |
MIT License | Mozilla Public License 2.0 |
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
next-mdx-remote
-
Give your blog superpowers with MDX in a Next.js
next-mdx-remote
- Is there a way to change where components are loaded from?
-
Making a blog with Directus, MDX, and Next.js On-Demand ISR
We are going to be using next-mdx-remote for this tutorial. Let us install it -
-
NextJS MDX from Database
So, i was reading the docs and Next/MDX looks exactly what i need for my blog. Well, not exactly because having hundreds of Markdown Pages doesn't look the best way to store the pages, and i was wondering if are any way to generate those pages from a DataBase full of Markdown pages. I read about next-MDX-remote but i was wondering if is there a native way to do that.
-
Next.js + MDX
next-mdx-remote, a community package maintained by Hashicorp that allows you to use MDX from outside your project.
-
Powerful Code Blocks with Code Hike and MDX
Do note that Code Hike also works with Next MDX Remote and MDX Bundler however, we are going to look at a simple example with the official MDX plugin for Next.js.
-
How to setup a dev blog using Next.js and next-mdx-remote.
Refer the next-mdx-remote github to learn more the use of plugins and how awesome things could be done using MDX.
-
Define my Pages in Wordpress
You could try storing mdx in wordpress somehow (I'm not a wordpress expert) and using next-mdx-remote to render that at runtime. MDX can contain both markdown and react components.
-
Beginners Guide to Using mdx-bundler With Your Next.js Blog
MDX is an extension on Markdown which, lets you import custom React components into your blog posts. To use MDX with Next.js you need to use a separate package. There are a few choices with MDX-remote being a popular one, but it has some drawbacks. For that reason, I chose to use mdx-bundler.
-
Adding an in-browser code preview to your React Application with Sandpack
Sandpack is a live coding environment that runs on the browser. It is made by the team behind CodeSandbox/. The main objective here is to provide interactive examples to play around with, to users. I see it being widely used in things like blog posts and documentation (in fact the, work in progress, new React Docs is using Sandpack). In this article, we are going to look at how to add Sandpack to a React Application and then we will look at integrating it with Next MDX Remote in a NextJS Application.
What are some alternatives?
next-offline - make your Next.js application work offline using service workers via Google's workbox
mdx - Markdown for the component era
next-seo - Next SEO is a plug in that makes managing your SEO easier in Next.js projects.
mdx-bundler - 🦤 Give me MDX/TSX strings and I'll give you back a component you can render. Supports imports!
Next.js - The React Framework
prism-react-renderer - 🖌️ Renders highlighted Prism output to React (+ theming & vendored Prism)
sqlite-worker - A simple, and persistent, SQLite database for Web and Workers.
rehype-prism - rehype plugin to highlight code blocks in HTML with Prism (via refractor)
Sentry-Picam - A simple wildlife camera for Raspberry Pis.
tailwind-nextjs-starter-blog - This is a Next.js, Tailwind CSS blogging starter template. Comes out of the box configured with the latest technologies to make technical writing a breeze. Easily configurable and customizable. Perfect as a replacement to existing Jekyll and Hugo individual blogs.
rehype - HTML processor powered by plugins part of the @unifiedjs collective
next-mdx-enhanced - A Next.js plugin that enables MDX pages, layouts, and front matter