Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

@parcel/resolver-default: Could not find extended tsconfig #9057

Closed
maxburs opened this issue May 30, 2023 · 1 comment 路 Fixed by #9419
Closed

@parcel/resolver-default: Could not find extended tsconfig #9057

maxburs opened this issue May 30, 2023 · 1 comment 路 Fixed by #9419

Comments

@maxburs
Copy link

maxburs commented May 30, 2023

馃悰 bug report

If the file in tsconfig.json#extends is resolved through a package name, @parcel/resolver-default throws. Regression occurred between 2.8.3 and 2.9.1 (new resolver?). Removing the "main" field in the repros package.json also makes it go away.

Here's the error created by the repro I've linked to below:

image

Maybe it's because our base config is in a package?

馃帥 Configuration (.babelrc, package.json, cli command)

tsconfig.json

{
  "extends": "@tsconfig/recommended/tsconfig.json"
}

package.json

{
  "name": "parcel-tsconfig-extends-repro",
  "packageManager": "yarn@3.5.1",
  "scripts": {
    "build": "parcel build ./src/index.ts"
  },
  "main": "dist/index.js",
  "devDependencies": {
    "@tsconfig/recommended": "^1.0.2",
    "parcel": "^2.9.1"
  }
}

馃 Expected Behavior

馃槸 Current Behavior

馃拋 Possible Solution

馃敠 Context

馃捇 Code Sample

yarn build fails in the linked repo. If you rollback the Parcel version to 2.8.3, it succeeds.

https://github.com/maxburs/parcel-tsconfig-extends-repro

馃實 Your Environment

Software Version(s)
Parcel 2.91
Node v16.20.0
npm/Yarn Yarn 3.5.1
Operating System macos
@bradleat
Copy link

Bumping this for visability. Is there anything in progress here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants