rsnext/test/integration/jsconfig-paths
Jan Potoms 683db9a8ad
Support tsconfig paths without baseurl (#34926)
tsconfig behaves differently with `tsc` vs. Next.js. When `baseurl` is omitted, `paths` should be resolved against the tsconfig location. Consequentially, in this case the paths must start with `./`. This PR aligns Next.js behavior with `tsc` around `paths` without `baseurl`. 

Related: https://github.com/microsoft/TypeScript/pull/40101
2022-08-15 13:33:25 +00:00
..
components Add test for single alias (#11296) 2020-03-23 12:30:42 -04:00
lib Update to filter loader specific files from traces (#32267) 2021-12-14 10:41:10 -06:00
node_modules/mypackage Update to filter loader specific files from traces (#32267) 2021-12-14 10:41:10 -06:00
pages Fix wildcard paths causing infinite resolving (#12318) 2020-04-29 17:04:42 +02:00
test Support tsconfig paths without baseurl (#34926) 2022-08-15 13:33:25 +00:00
.gitignore Fix wildcard paths causing infinite resolving (#12318) 2020-04-29 17:04:42 +02:00
jsconfig.json Fix wildcard paths causing infinite resolving (#12318) 2020-04-29 17:04:42 +02:00
next.config.js Enable "paths" support by default (#11970) 2020-04-17 16:28:17 +02:00