next-mdx-enhanced
esbuild-config
next-mdx-enhanced | esbuild-config | |
---|---|---|
3 | 8 | |
494 | 73 | |
- | - | |
3.3 | 0.0 | |
about 1 year ago | over 1 year ago | |
JavaScript | Rust | |
Mozilla Public License 2.0 | 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-mdx-enhanced
-
Quick comparison of MDX integration strategies with Next.js
Like @next/mdx, you add next-mdx-enhanced to the project by exporting a function in the project's next.config.js file.
-
How I Made My Multilingual Blog
I don't have any experiences with the other libraries (e.g. next-mdx-enhanced, next-mdx-remote) so I won't judge the pros and cons of one compared to the others.
-
Release v0.9.0 · Evanw/Esbuild
React & next.js are worth evaluating. It's a super powerful full stack with everything from server side rendered data (REST APIs even) all the way to complete SPAs, all using the same react components. It's a slick little swiss-army knife that can make anything from a basic blog with markdown content, to a static marketing page, to a full client-first PWA experience.
MDX is another neat step, it's markdown + react components and fits in very well with next.js: https://github.com/hashicorp/next-mdx-enhanced
Vue, and Svelte to just get an idea of what other components systems are like. They're all equally capable and just have different tradeoffs and styles. Keep an eye on Svelte in particular as its next.js-like system (SvelteKit) is working on a major revamp to be serverless-first and is quite interesting. Once you learn one component system it's easy to switch between them all--they're all cribbing and building on top of each other's ideas. The whole space is innovating in a great way.
Web components are tood to learn and compare to component frameworks above. It's still a changing space but points to a nice future where we can all just publish and share components.
esbuild-config
- Show HN: esbuild-config − Config files for esbuild
- esbuild-config
- esbuild-config: Config files for esbuild
- esbuild-config: config files for esbuild
- Show HN: esbuild-config
-
Release v0.9.0 · Evanw/Esbuild
Shameless plug: esbuild-config allows you to declare your esbuild config as a JSON file.
https://github.com/bpierre/esbuild-config
- Show HN: esbuild-Config
What are some alternatives?
next-mdx-remote - Load mdx content from anywhere through getStaticProps in next.js
vite - Next generation frontend tooling. It's fast!
mdx-bundler - 🦤 Give me MDX/TSX strings and I'll give you back a component you can render. Supports imports!
sst - Build modern full-stack applications on AWS
Snowpack - ESM-powered frontend build tool. Instant, lightweight, unbundled development. ✌️ [Moved to: https://github.com/FredKSchott/snowpack]
esbuild - An extremely fast bundler for the web
snowpack - ESM-powered frontend build tool. Instant, lightweight, unbundled development. ✌️
leerob.io - ✨ My portfolio built with Next.js, Tailwind, and Vercel.
react-relay - Relay is a JavaScript framework for building data-driven React applications.
mdx - Markdown for the component era