Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

fix: update module resolution for non-relative paths#229

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

smoores-dev
Copy link
Contributor

@smoores-devsmoores-dev commentedJun 20, 2023
edited
Loading

Fixes#227.

This change generalizes "module resolution with failed lookup locations" so that it works for newer implementations of the typescript language server, which provide such information in the response forresolveModuleNameLiterals, rather than implementing a separategetResolvedModuleWithFailedLookupLocationsFromCache.

Tested locally in a project using Typescript 5 and path aliases, and imports like:

import{editorContainer,tableOfContentsContainer,}from"@/components/app.module.css"

which were failing before this change now successfully show type information and support "Go to Definition", etc.

marcoms reacted with heart emoji
@smoores-dev
Copy link
ContributorAuthor

Hey@mrmckeb! I imagine you've got a ton of other stuff going on, but let me know if you have a chance to take a look at this any time soon! I'd love to get your thoughts. Thanks so much for all of your work on this plugin!

@LoiLock
Copy link

Any updates?

@smoores-dev
Copy link
ContributorAuthor

Hey@mrmckeb! I just wanted to check in and see whether you might have a chance to take a look at this PR sometime soon!

Copy link
Owner

@mrmckebmrmckeb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Thanks@smoores-dev - this looks great to me. Sorry for the very slow turnaround, I try to check in once every 2-3 weeks (unless there's a critical issue) but had a bit more going on recently.

@mrmckebmrmckeb changed the titleFix module resolution for non-relative paths in newer tsserver implementationsfix: update module resolution for non-relative pathsSep 22, 2023
@mrmckebmrmckeb reopened thisSep 22, 2023
@mrmckeb
Copy link
Owner

Closing and reopening to trigger tests, etc.

@mrmckebmrmckeb merged commite21ae36 intomrmckeb:mainSep 22, 2023
@mrmckeb
Copy link
Owner

I plan to get this out in the next day or two - I also need to set up automatic releases for this repo.

marcoms reacted with thumbs up emoji

@mrmckeb
Copy link
Owner

Sorry this took so long. Released:
https://github.com/mrmckeb/typescript-plugin-css-modules/releases/tag/v5.0.2

smoores-dev reacted with heart emoji

@smoores-devsmoores-dev deleted the typescript-5-paths-support branchOctober 16, 2023 16:08
sungik-choi added a commit to sungik-choi/bezier-react that referenced this pull requestDec 12, 2023
sungik-choi added a commit to sungik-choi/bezier-react that referenced this pull requestDec 13, 2023
sungik-choi added a commit to sungik-choi/bezier-react that referenced this pull requestDec 13, 2023
sungik-choi added a commit to sungik-choi/bezier-react that referenced this pull requestDec 14, 2023
sungik-choi added a commit to sungik-choi/bezier-react that referenced this pull requestDec 15, 2023
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@mrmckebmrmckebmrmckeb approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Autocomplete not working with global path
3 participants
@smoores-dev@LoiLock@mrmckeb

[8]ページ先頭

©2009-2025 Movatter.jp