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.

Sign up for GitHub

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

Jump to bottom

Error with TS Paths in vscode with Storybook (@ alias) #522

Closed
mckernanin opened this issue Feb 27, 2020 · 1 comment
Closed

Error with TS Paths in vscode with Storybook (@ alias) #522

mckernanin opened this issue Feb 27, 2020 · 1 comment
Labels
problem: stale Issue has not been responded to in some time scope: templates Related to an init template, not necessarily to core (but could influence core) solution: duplicate This issue or pull request already exists

Comments

@mckernanin
Copy link

Current Behavior

When creating a new project with the React/Storybook preset, VSCode has issues with resolving path aliased modules. Storybook runs successfully, VSCode just isn't picking up the config properly.

image

Expected behavior

Out of the box everything should "just work™️" without any configuration.

Suggested solution(s)

A few solutions, ranked in order of preference:

  1. Provide documentation / default settings which make things like import component from '@'; work properly
  2. Don't use path alias by default (unfortunate, but there shouldn't be usability issues out of the box)

Additional context

Your environment

Software Version(s)
TSDX 0.12.3
TypeScript 3.8.2
Browser n/a
npm/Yarn yarn v1.22.0
Node 12
Operating System Mac OS
VS Code 1.43.0-insider
@agilgur5
Copy link
Collaborator

Sounds like a duplicate of #431 which was fixed by #435 but still has yet to be released (c.f. #512 )

@agilgur5 agilgur5 mentioned this issue Mar 4, 2020
Closed
@agilgur5 agilgur5 changed the title Error with TS Paths in vscode Error with TS Paths in vscode with Storybook (@ alias) Mar 9, 2020
@agilgur5 agilgur5 added solution: duplicate This issue or pull request already exists problem: stale Issue has not been responded to in some time labels Mar 9, 2020
@agilgur5 agilgur5 closed this as completed Mar 9, 2020
@agilgur5 agilgur5 added the scope: templates Related to an init template, not necessarily to core (but could influence core) label Sep 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
problem: stale Issue has not been responded to in some time scope: templates Related to an init template, not necessarily to core (but could influence core) solution: duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@agilgur5 @mckernanin