0ct0pu5/ente
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Next.js does not use Babel (at least for single file) anymore

Browse source 
> Compiling using Next.js compiler instead of Babel is enabled by default since v12

https://nextjs.org/docs/architecture/nextjs-compiler
This commit is contained in:
Manav Rathi 2024-02-15 12:05:56 +05:30
parent f3340db57e
commit 3fad0427a7
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
packages/utils/tsconfig.json
View file

@ -10,15 +10,15 @@
*
* In our case, we tell it that the code will run in a modern browser,
* and will have access to a latest JS (esnext) and the DOM (dom). Our
* transpiler (Babel via Next.js) will take care that these things hold.
* transpiler (Next.js) will ensure that these things hold.
*
* Unlike the other individual library components (say how "esnext"
* implies "esnext.*"), "dom.iterable" (the ability to iterate over DOM
* elements) is not a subset of "dom" and needs to be listed out
* explicitly.
*
* Note that we don't need to specify target, since TypeScript isn't
* actually generating (emitting) the JavaScript.
* Note that we don't need to specify the `target` compilerOption, since
* TypeScript isn't actually generating (emitting) the JavaScript.
*/
"lib": ["esnext", "dom", "dom.iterable"],
@ -47,7 +47,7 @@
"jsx": "preserve",
/* Ask TypeScript to warn us if we use TypeScript features that cannot
be used by single-file transpilers (Babel in our case) */
be used by single-file transpilers */
"isolatedModules": true,
/* Enable various workarounds to play better with CJS libraries */
"esModuleInterop": true,