next-optimized-images
microsite
next-optimized-images | microsite | |
---|---|---|
11 | 5 | |
2,193 | 879 | |
- | - | |
0.0 | 0.0 | |
over 1 year ago | over 1 year ago | |
JavaScript | TypeScript | |
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-optimized-images
-
Auth.js Authentication for the Web
Same. I found this example [1] particularly helpful, although I don't know how good this [2] library it uses is. Overall, I've seen multiple OSS projects [3] that try to support a missing functionality in Next.js seem to just give up trying to keep up with their breaking changes.
[1] https://stackblitz.com/edit/github-mwzv1t?file=README.md
[2] https://github.com/hoangvvo/next-connect
[3] https://github.com/cyrilwanner/next-optimized-images
-
Should I use Create React App, or ViteJS?
But yes, it felt more finnicky if that makes sense. I'd suggest building your own image thing using next-optimised-images to suit your exact preferences. You can generate a blurred low res image, a higher res version and overlap them together to essentially re-create a lite version of Image component : https://github.com/cyrilwanner/next-optimized-images
-
Serverless Next.js on AWS with Terraform 1.1
Next.js component is not supported (see Next.js Image loader). Use img instead. The sample project is already set up to use next-optimized-images which can instead be used to serve images.
-
Day 52 of 100 Days of Code & Scrum: Back From Break, Now Stuck on next/image Static Page Issues
next-optimized-images
-
Is it just me or is Gatsby SUPER fragile ;
next.js actually does images even better in my experience, There's no magical Gatsby Image plugin but you can use next-optimized-images which will give you all the raw materials such as traced SVGs, etc and you can build your own image component around that very easily which you have full style control over.
-
Next.js 11.1: ES Modules support, Rust-based tooling, Improved Build Performance
We aren't using anything at the moment but you can use for example https://github.com/cyrilwanner/next-optimized-images
-
Next.js 11
That's why I removed next/image and ended up using https://github.com/cyrilwanner/next-optimized-images
That lets you export the images pre-optimized for different sizes/etc. You can then do a normal next export.
-
Next.js 10.2 ā Improved Performance, Accessibility, Automatic Font Optimization
You can still use `next/image` when outputting a static site, as long as you use `next start`. Using `next export` removes the server entirely, meaning you can't optimize images on demand.
There's an open issue to explore optimizing images at build time, but for now, you can use https://github.com/cyrilwanner/next-optimized-images
-
TheVECentre.com
TheVECentre.com is predominately built using Next.js and Tailwind CSS. Two Next.js plugins, next-seo and next-optimized-images, to handle the SEO orientated properties and optimise images for different device sizes respectively. Additionally, React Icons supplies any social icons, EmailJS powers the contact form and Framer Motion adds animations to the site.
-
ImageMagick, TinyPNG, WebP... What are your best practices for image optimization?
I like your style š Im using next.js for incremental static regeneration . I've been going down rabbit hole after rabbit hole regarding image optization. I found this, https://github.com/cyrilwanner/next-optimized-images .
microsite
- Next.js 11
- Is there a React Framework to build Static Non-React website?
-
Ask HN: What Are You Working On?
None are ready for the public yet, but all in the hopper or under serious consideration:
- Personal site/blog with a bunch of algorithmically generated art and other fun stuff, built on Node/Preact but progressively enhanced/almost completely JS-free at runtime. Motivation for the build approach is that Iām on the low/no client JS static site bandwagon but I quite like the DX of JSX components and CSS-in-JS.
- Iām using a few excellent existing tools[1][2] for said site which unfortunately arenāt designed to work well together, so I have a variety of wrapper tooling that makes them live peacefully together. Iām also developing a bunch of other build-stage tools for my use cases. I plan to open source (or hopefully contribute back) all of that as soon as Iām satisfied with their quality.
- A set libraries for building declarative, type safe, automatically validated/documented service API boundaries (HTTP/REST to start, but I also plan to support other transport protocols) ā think io-ts[3] type interfaces but you get swagger docs for free in a transport-agnostic interface. Iāve built this kind of thing before, it was wildly successful in real world use, but itās proprietary to a previous employer and Iām starting over with all the stuff I learned in hindsight.
- A ānag meā app thatās basically āreading listā plus āremindersā with minimal config, eg ānag me soonā or ānag me after a whileā. My personal use case is I frequently screenshot/text myself/etc stuff I want to look at later (usually on phone but need a computer to dive in), then it just goes down the memory hole. Iāve tried setting reminders but itās often too much fuss, and Iām far too ADHD to use a passive list.
- Exploring building yet another FE build tool/bundler thatās explicitly multi-stage/sequential with static input/output validation, per-step/time travel debugging. Motivation is that existing tools are just a big ball of config magic and totally inscrutable. Iād likely wrap existing build tools because their set of responsibilities isnāt my motivation and I donāt want to introduce that much more new API surface area to weary FE devs.
[1]: https://github.com/natemoo-re/microsite
-
Repos interesantes de la semana #1
Microsite es un generador de sitios estƔticos (SSG) construido sobre Snowpack y que utiliza Preact como framework.
What are some alternatives?
Next.js - The React Framework
astro - The web framework for content-driven websites. āļø Star to support our work!
patch-package - Fix broken node modules instantly šš½āāļøšØ
next-transpile-modules - [ARCHIVED] Next.js plugin to transpile code from node_modules
next-super-performance - The case of partial hydration (with Next and Preact)
react-icons - svg react icons of popular icon packs
hubs - Duck-themed multi-user virtual spaces in WebVR. Built with A-Frame.
squoosh - Make images smaller using best-in-class codecs, right in the browser.
yassg - A super simple static site generator written in python.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
mapbox-gl-js - Interactive, thoroughly customizable maps in the browser, powered by vector tiles and WebGL