-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add support for value variables '@value' and fix default exports #6
base: master
Are you sure you want to change the base?
Conversation
@@ -16,7 +16,7 @@ program | |||
.version(version) | |||
.usage('[options]') | |||
.option('-b, --base <path>', `default base is ${ defaults.base }`) | |||
.option('-i, --sass-include <paths>', `list of paths to includedefault is ${ defaults.sassInclude }`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, is this a typo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see, yes. Thanks
@@ -31,10 +31,11 @@ const toCamelCase = ( str: string ) => str.replace(/-+(\w)/g, ( _match, firstLet | |||
|
|||
const getDtsContent = async ( sassInclude: string[], sassData: string, includeIndexKey: boolean, path: string ) => { | |||
try { | |||
const fileData = fs.readFileSync(path, 'utf-8') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer a non-blocking solution
This is a naive approach to add support for value variables. I dont expect the PR to be merged as-is, but I hope this will start a conversation for proper support for
@value
and eventually the:export
selector.Additionally, I fixed the
The expression of an export assignment must be an identifier or qualified name in an ambient context.
the default export declaration.