If anything goes wrong, feel free to dm or ping me!
next.config.mjs → next.config.ts
(now available on next@canary)
00:00
Jiwon Choi
381 posts
- The latest release of @nextjs v14.2.5 also had a small win for performance, expect ~400ms reduced boot time running next dev --turbo!
- Can't wait to ship this! 😆✨ Introducing Typescript support for next.config.js in Next.js 15 h/t to @devjiwonchoi for his first major ship as a member of the Next.js team. What an exciting start! ◆ Native support for next.config.ts (and other TS file extensions). ◆ HMR on config changes. ◆ Available
- It's been a year since this PR was merged on @nextjs, which was the first big step of my open-source journey. That moment of being notified that the PR has been merged is... I hope more people can feel what I've felt.
- How to run a TS file in 2024: > npx tsx How to build a package in 2024: > npx bunchee
- Replying to @feedthejimHey everyone, feel free to ping me if you have any suggestions or questions. 😄
- Replying to @devjiwonchoi and @nextjsThe beauty of open source is that you can collab with people on the other side of the globe who you've never met, gathered only with passion and love for the community. The best part is that you can see how the best engineers work and learn from them, at no cost. It's crazy.
- I casually go back and read @kdy1dev's blog post about "criticizing doesn't require an alternate solution". It is worth reading it even with a translator. He emphasizes that our goal isn't to refute one's criticism but to derive a solution altogether. kdy1.dev/2023-7-23-crit…
- The two primary advantages are: 1. Importing types for type-checking instead of using JSDoc. 2. Running TypeScript files during the initial phase.
- Replying to @devjiwonchoikind.engineering my 5 takeaways: - be honest, open about my life to help build trust - provide clear ways to improve instead of white lies - ask for criticism, thank them as it was probably hard - sync directly if a lot of comments needed - address nitpicks as "nitpicks"
- Replying to @leerob and @leeerobWould love to see a video of contributing to Next.js codes as described in: github.com/vercel/next.js… The following video is awesome, but as it covers fixing the docs, I'd love to see the workflow on the actual codes! youtube.com/watch?v=cuoNzX…
