Skip to content

feat: sass support for tsconfig path aliases #105

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

Merged
merged 1 commit into from
Nov 2, 2020

Conversation

WOOLAN
Copy link
Contributor

@WOOLAN WOOLAN commented Oct 14, 2020

Fixes #98

Tried to find a way to use TypeScript to resolve the paths, but I could not. Did not want to implement the logic myself, hence a new dependency tsconfig-paths. Feedback welcome.

@WOOLAN WOOLAN force-pushed the feature/sass-tsconfig-paths branch from 9df507f to 51ed23e Compare October 14, 2020 10:45
@mrmckeb
Copy link
Owner

mrmckeb commented Nov 2, 2020

Sorry for the delay @WOOLAN, this looks great - I'll release it shortly!

@mrmckeb mrmckeb merged commit d9afa51 into mrmckeb:develop Nov 2, 2020
@WOOLAN
Copy link
Contributor Author

WOOLAN commented Nov 2, 2020

Thanks, no worries.

I read that baseUrl will no longer be required in TypeScript 4.1 and am therefore taking another look at this. Currently my fix requires baseUrl to be set in compilerOptions.

I might also have found a way for TS itself to resolve the paths which would mean that we could drop the dependency on tsconfig-paths. Should hopefully make this plugin more future proof against TS updates to baseUrl/paths.

My hope is to get it done in the next week or two. I'll submit another PR when ready.

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

Successfully merging this pull request may close these issues.

Consider TS path aliases for Sass
2 participants