4 ms·
Lee from the Next.js team here. Could you share what features you’d like to see? Is there a GitHub issue or more information about the TypeScript declarations?
by leerob 5y ago
Lee from the Next.js team here. Could you share what features you’d like to see? Is there a GitHub issue or more information about the TypeScript declarations? Thank you!
- brundolf 5y agoThere aren't currently any actual features I'm missing; I find Next tends to get updated pretty promptly. I just remember at least one case where Webpack or React or something had a feature I wanted to use and there's always this question of "well but does it work in Next yet?", and there was a GitHub ticket for it but the answer was "not yet". Such is often the cost of using an all-inclusive framework. As for the TypeScript types, there are just several parts that are not as thoroughly typed as they could be; there are some `any`s, and just yesterday I got bit by passing an invalid event name to router.events.on(). The first argument is typed `string` when it could have been a union type with the exact event names that are valid, which would have caught the error before it got to our QA environment. Just stuff like that. I should note that we aren't on the latest version of Next, so it's possible the situation has improved. And assuming it hasn't, I've thought about submitting a PR myself with some improvements to the declarations. Overall, though, it's a great framework!
- leerob 5y agoWe've landed the TS improvments you're looking for! https://github.com/vercel/next.js/pull/26456 https://github.com/vercel/next.js/pull/26456