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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin fails if no baseUrl is supplied #6

Closed
bradzacher opened this issue Oct 24, 2018 · 1 comment
Closed

Plugin fails if no baseUrl is supplied #6

bradzacher opened this issue Oct 24, 2018 · 1 comment
Assignees
Labels

Comments

@bradzacher
Copy link
Collaborator

originally reported by @jhnns
#2 (comment)


After upgrading to 1.1.0 I get these errors in every file:

Resolve error: Unable to find tsconfig in /my/project/path: Missing baseUrl in compilerOptions import/no-unresolved
When I set...

"baseUrl": ".",
this plugin works fine. The problem is, however, that VSCode now generates paths on auto import that webpack and Node.js are not able to resolve:

// Instead of
import something from "../../shared/something";
// I get
import something from "src/shared/something";
I'm not sure if VSCode auto import is doing the right thing here, but I also think that baseUrl doesn't have to be set if I'm not using the paths option.

@bradzacher bradzacher added the bug label Oct 24, 2018
@bradzacher bradzacher self-assigned this Oct 24, 2018
bradzacher added a commit that referenced this issue Oct 26, 2018
@jhnns
Copy link

jhnns commented Nov 6, 2018

Thank you, works like a charm ✨ 👍

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

No branches or pull requests

2 participants