Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
leerob
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
47 ms
·
631.
▲
by
leerob
7y ago
I was blown away with the reaction to my tweet about Next + Prisma [0], so I wrote up a full tutorial explaining how to create a static site with direct database access using Next's `getStaticProps`. Let me know if you have any questio
632.
▲
Static Sites with Next.js 9.3 and Prisma
(leerob.io)
1 points
by
leerob
7y ago
|
1 comments
633.
▲
by
leerob
7y ago
I absolutely love your site's design and content. The photographer in me is so happy.
634.
▲
by
leerob
7y ago
I really enjoy your posts. Keep up the great work.
635.
▲
by
leerob
7y ago
https://leerob.io/blog I write about web development, tech careers, and a bit about my personal life. Lots of JavaScript, React, Next.js, and UI/UX related topics. Fun tech facts on my site. It's a hybrid Next.js
636.
▲
by
leerob
7y ago
This was fascinating! I also read some of your other posts and thoroughly enjoyed the content. Great work. Related – If anyone wants to learn more about Next.js, my course is free right now while everyone's stuck indoors. https:/
637.
▲
Improving My Next.js MDX Blog
(leerob.io)
2 points
by
leerob
7y ago
|
0 comments
638.
▲
by
leerob
7y ago
The difference is that Next.js is very unopinionated. GraphQL, Prisma, SQL – these are opinionated choices from Redwood and largely the point of the framework.
639.
▲
by
leerob
7y ago
Is Redwood _not_ limited to browsers?
640.
▲
by
leerob
7y ago
Both Next.js and Gatsby are great to work with. If you're looking to stay in the JS ecosystem, you'll be happy with either choice. As for which is "easier", it comes down to your skill set and preference. If you're
641.
▲
by
leerob
7y ago
Wow, this is incredible! I'll have to try it out.
642.
▲
Next.js 9.3 – Static Site Support, 32 KB Smaller Runtime
(nextjs.org)
174 points
by
leerob
7y ago
|
29 comments
643.
▲
Create a Dashboard with Next.js API Routes – Fetching Data with SWR
(leerob.io)
2 points
by
leerob
7y ago
|
0 comments
644.
▲
by
leerob
7y ago
It doesn't appear that GitHub has announced anything about Discussions on their site yet. My guess is that a few select large repositories (e.g. zeit/next.js) are trying out the beta to provide feedback. We'll probably get so
645.
▲
by
leerob
7y ago
I had the same thought. Especially since the Next.js maintainers said that Discussions would eventually replace their Spectrum community. Maybe GitHub acquired Spectrum with the intention of slowly migrating its userbase over.
646.
▲
by
leerob
7y ago
Previous discussion: https://news.ycombinator.com/item?id=15838270
647.
▲
How Stripe Designs Beautiful Websites (2017)
(leerob.io)
2 points
by
leerob
7y ago
|
1 comments
648.
▲
by
leerob
7y ago
No worries – thank you! It's been quite an adventure. The course turned out to be more work than I expected, but I'm proud of what I've accomplished.
649.
▲
by
leerob
7y ago
The first introduction module is 100% free if you want to check it out. Introduction to Next.js (Next vs. Gatsby vs. CRA) [26:06] - https://www.youtube.com/watch?v=uQeidE2LA1s
650.
▲
Show HN: I just launched my first video course (React/Next.js)
2 points
by
leerob
7y ago
|
3 comments
651.
▲
Iowa Caucuses Should Not Have Used an App
(leerob.io)
1 points
by
leerob
7y ago
|
0 comments
652.
▲
Create a Dashboard with Next.js API Routes - YouTube API
(leerob.io)
1 points
by
leerob
7y ago
|
0 comments
653.
▲
Create a Dashboard with Next.js API Routes – Unsplash API
(leerob.io)
1 points
by
leerob
7y ago
|
0 comments
654.
▲
by
leerob
7y ago
It is! https://github.com/leerob/leerob.io
655.
▲
by
leerob
7y ago
Hey, thanks! Is your dashboard open-source?
656.
▲
Show HN: Inspired by open startups, I built an API-driven personal dashboard
2 points
by
leerob
7y ago
|
5 comments
657.
▲
by
leerob
7y ago
Google Drive. Might not be the best, but it is easy.
658.
▲
by
leerob
7y ago
https://leerob.io/
659.
▲
by
leerob
7y ago
The amount of content here is incredible. Did Apple create this, or fans?
660.
▲
by
leerob
7y ago
I was intentional about saying "not preferred" instead of "not supported". You are correct, there have not been any breaking changes, which is very helpful. When new features and changes roll out (like CSS support in 9.2
More ›