Hey #nextjs & #apollo devs! I wanted to start a headless #craftcms project with #graphl, nextjs & apollo. But I now discovered the app router changes in next + the experimental state of support https://www.npmjs.com/package/@apollo/experimental-nextjs-app-support Now thinking about REST / react-query. Any opinions?🤔
Vous connaissiez "Emprunte mon toutou" vous ? Moi pas et c'est bien dommage. Ca semble être une très bonne idée.
Ils recherchent un développeur web front end pour poursuivre les évolutions de l'application web actuelle et faire de nouveaux sites.
C'est du télétravail ou sur place sur Toulouse, au choix.
Continuing to be impressed by react-instantsearch ( https://www.npmjs.com/package/react-instantsearch ).
All of these filterable options auto-update based on what's in the results.
I'm seriously amazed by Typesense/Algolia's API and how well it maps to the the library.
The facets are based on every result in the collection – not just what's shown.
The search query returns the results + the facets.
If facets are collapsed, they won't be queried.
Seriously impressive. 👏
Prepisovani "firemni" casti webu @ceskodigital z Nextu do Webflow pokracuje. Zakladni definovani stylu slo dobre, temer vse v barvach, typografii a zakladnich mezerach pokryly globalni classy ("all h1", "all h2"...). Designerka to abstrahovala do design systemu moc pekne.
Sekce jsou naopak hodne custom. Mimo hlavicky a paticky se temer nic neopakuje, takze se to nesnazim sroubovat na nejakou abstrakci a sazim jednu sekci za druhou. WET princip. Pomuze to predatelnosti.
Hey! I’m a senior front-end developer looking for my next medium- to long-term freelance role.
Interesting read while I start to check out #nextjs again (at work): https://leerob.io/blog/using-nextjs#the-web-platform
The original article "Why I won't use Next.js" (and remix instead) was also discussed in this podcast: https://runtimerundown.com/episodes/the-one-about-not-using-nextjs
"Deploy a NEXT.js app for FREE on AWS with SST - DEV Community" https://dev.to/kumo/deploy-a-nextjs-app-for-free-on-aws-with-sst-3g28 #nextjs #aws #webdev
Listopad byla docela jizda. Ac na WRKS moc programatorske prace nebylo, vrhnul jsem se na web cz Aerorozvedky, web @ceskodigital a prednasky. Na prosinec a leden moc prace neni, ale flakat se u stromecku nehodlam, tak jsem se vrhnul na hunteni gigu.
Mam hromadu zkusenosti a kapacitu ~20h/tyden na programovani za penize. V Nextu, TypeScriptu, DevOps (AWS, skalovani), ale muzu se kouknout na cokoli je potreba vyresit.
Znate nekoho s peknym projektem? Prosim, nevahejte sdilet 🙏
#introduction I am a code-writing, #DnD loving #queer musical artist from SoCal based in Germany increasingly obsessed with #mentalhealth, #privacy, #digitalhumanities, & intercultural #ethics. Recovering #hustleculture addict.
Interview with John Faber of Chapter Three: Next-Drupal & securing the future of Drupal. https://www.agiledrop.com/blog/interview-john-faber-chapter-three-next-drupal-securing-future-drupal #Drupal #NextJS
🌎 Remote; Gerakas, Greece
📦 New release: next-usequerystate 1.13.0
It adds a couple of bug fixes, plus two new exciting features:
- A server cache to allow deeply nested #react server components to access search params in a type-safe manner (video coming up next week)
- Support for `useTransition` to get a loading boolean state on RSC updates.
just finalized an upgrade to the website: the fundraiser feature is now available.
spoiler, the #react app is buggy and comically inefficient. feel free to contribute.
#anarchy #anarchism #anarchist #communist #communism #common #anarchocommunism #anarchocommunist #libertarian #left #gauche #izquierda #sinistra #anarchia #comunismo #communisme #bike #bicycle #cycling #velo #bici #biking #hiking #trek #walk #train #trains #software #dev #developer #developers #devs #engineer #computer #network #programming #system #systems #linux #democracy #directdemocracy #solana #ubi #universalbasicincome #freedom #free #liberta #libre #liberdade #libertarianism #weed #marijuana #smoke #green #pot #joint #spliff #nuclear #energy #progress #progressive #progressivism #accelerationism #tryptamine #lsd #acid #hallucinogenics #hallucinogenic #reading #reader #read #books #book #literature #essays #research #information #learning #academia #university #student #worker #labor #labour #proletarian #proletariat #marx #gorz #malatesta #gay #gayboy #blockchain #rust #rustlang #react #nextjs #web #app #apps #webdev #webdesign #token #crypto #cryptography #micali #silviomicali #zkproof #zeroknowledge #zkproofs #petition #petitions #elections #referendum #census #council #lottocracy #representation #opensource #freesoftware #foss #floss #freeassange #palestine #freepalestine #acab
Searching for specific errors and issues with #nextjs is leading me to pages that trigger my "PHP help pages PTSD"
On Tuesday, I had an urge to work on a Next.js related content idea that formed in my head.
I spent some time this week hacking on it, and reached "minimum viable blog post". 😂
That point where the styles and data hit the get to where, if you squint, you can see where things are going.
I'm going to share while still in the ugly state (it'll only get better from here 😅).
Quick Next.js answers when you need them most.
I’ve been having so much fun building in Next.js the past 2.5 years. It reminds me of Rails from 2006 again. I’m even thinking about making some educational content!
The thought of building an audience and creating something big sounds exhausting. 😮💨 I’m thinking something basic that solves common problems w/video+text.
I’d be curious to know: what questions, or problems have you faced working in Next.js that you wish you had a quick answer to?
Hello world 👋
I'm Jon, an 18-year-old #programming enthusiast from #switzerland. I caught the coding bug at age 12 😉, and I've been fascinated with computer science ever since. #webdevelopment has become my passion.
I'd love to connect!
Ca c'est de la stack !
Est-ce que des #devs ont déjà eu ce cas là ?
Dnes se mi opet bohate vyplatila investice do typovanych API endpointu na FE i BE. Zmena v mechanismu automatizace obrazku a videi v ruznych velikostech se propsala z jednoho zdroje na BE i FE.
Dneska uz si neumim predstavit tu udrzbu kodu bez dobre nastaveneho typovani.
Taky zacinam preferovat knihovny, ktere pouzivaji nativne Zod pro typovani. Je skoda, ze DB frameworky jako Prisma generuji "dale nepouzitelne" typy a nejdou posilat typovana views mezi BE a FE.
Tak hlasim vitezstvi nad service-workery a web push notifikacemi na vsech platformach.
🎯 Vsude se da k notifikacim prihlasit s kompletne pokrytou sadou moznych chyb a logovani.
🎯 Notifikace spravne otevira PWA, ac na iOS (16.7) ji nedokazu deep linkovat. Podle specifikace by to melo jit.
🎯 Minimalizoval jsem vsecky side-effekty, ktere by service-worker mohl mit a neco mi v apce rozbijet. Celkove jsem dosahl rozumneho kodu.
Velka PWA bariera padla i na iOS 🍾
📝 Why You Should Write Your Own Static Site Generator
「 When Vercel released Next.js 14 recently, some friends I've talked to where still on Next.js 12 and really felt the pressure to upgrade to not fall behind even more. This made me think about the longevity and robustness of my website and so I decided I don't want to depend on other people's decisions and run after version upgrades I don't care about 」
✍️ New blog post: "Testing against every Next.js canary release"
After one of the recent canaries broke next-usequerystate, I need to know when it gets fixed and when other things break again in the future.
So I made a little cron script to poll the GitHub releases API and trigger a GitHub Actions workflow run when they publish a release.
Po mesici na Mastodonu prisel cas na #introduction
Jsem programator z Liberce. Pracoval jsem pro ziskovky i neziskovky ruzne po svete. Pro B&MG Foundation v Keni, v >c.d, vytvarel jsem Zbrane pro Ukrajinu a podobne. Aktualne programuju vlastni socialni sit WRKS.
V tech stacku mam TypeScript, Next, AWS, databaze a v podstate vsecko kolem toho.
✍️ Pisu pravidelne o vsem, co mi prijde pod ruku.
☢️ Why I Won't Use Next.js
➥ Kent C. Dodds
「 OpenNext exists because Next.js is difficult to deploy anywhere but Vercel. I'm not making moral judgements here. I appreciate the company’s incentives to make their own hosting offering as attractive as possible, but it’s evident that this incentive has deprioritized making Next.js easy to deploy anywhere 」
I'm not talking about the blogposts, Remix is just lashing out while having its own set of problems.
Pretty they would act the same if they could.
With Remix you may as well roll your own framework given how things are under VC/Corporate frameworks lately, specially niche "opensourcy" ones.
☢️ If you're building on Next.js, get out while you can. One point of failure, Big VC Opensource Energy.
They're already pulling the rug on different parts of its framework, making them only feasible on Vercel.
Extreme conflict on interests.
Small revenues to justify those expensive engineers and devrel.
They're chockholding the React community, like Meta wasn't bad enough already.
Trying to be the AWS of React isn't a good look tbh.
🗞 New episode of Changelog News!
👀 React Server Actions on display at Next.js Conf
🛑 @kentcdodds on why he won't use Next
🟢 Lee Robinson on why he is using Next
📦 @nixos_org' reproducible builds
✍️ OpenSign is an open source alternative to DocuSign
🎙 hosted by @jerod
#NextJS, known as the React framework for the web, has launched its 14th version with new features, enhancements, and bug fixes. Key advancements include the experimental preview of partial prerendering and a stable implementation of Server Actions.
So far, it looks like it needs:
- A database where to store follower connections, so we can send them activities
- A POST endpoint for the inbox (to accept follow requests)
- A GET endpoint for the outbox (to do server-to-server federation when publishing a post)
Partial Prerendering is one of the coolest things to happen to nextjs. I cannot wait for it to stabilize. https://nextjs.org/blog/next-14#partial-prerendering-preview
Also it's built by one of my old teams and they're really great people who are digging us out of some of the oldest serverless tradeoffs (like the lack of streaming!). Building on top of a team I used to manage a *long* time ago who have made some impossible stuff possible with serverless. I'm really proud of all of them. 💓
Looks like #nextjs 14.0.0 just dropped about 20 minutes ago on npm... I'm guessing they'll mention that at the keynote!
I was reading this article about why someone should not use Nextjs 13, and only two things make good points: it was a premature release, and the transition from pages router to API router is complicated.
A better title should be "Use SvelteJS instead of Nextjs."
📣 There is still time to attend ComposableNOW in Lille, France – the FREE DrupalCon Lille Day0 event, at Lille Grand Palais. Don't miss the sessions on decoupled, Drupal, and composable architectures, starting at 2:00 PM CEST.
👉 Register now: https://www.amazee.io/composablenow-2023/
- Experienced with #TypeScript / #NestJS / #NextJS / #React & more!
- Delivered 15+ projects to millions of users
- Flexible rates depending on mission length and complexity
- Based in France, I speak 🇫🇷 and 🇬🇧 fluently
And the complexity comes from the need and desire to try to keep the code splittable and tree shakeable, so that the tooling can keep sizes down.
While at the same time you try to keep the DX as simple as possible. And these two goals are just in immense conflict with each other.
In one side you have this: https://github.com/vitejs/vite/issues/1579
Yay, just add import CSS!
But then you try to consume such a lib in #NextJS and you face this:
You can never win. Only suffer.
The more I work with React in general, and Next.js in particular, the more I despise it. If you live life to the fullest when you bathe in accidental, unintentional complexity, Next.js has got you covered. Lathered, as a matter of fact. From top to toe. Bleuch.