-
Notifications
You must be signed in to change notification settings - Fork 34
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
Suggestions: package improvements #140
Comments
These look good (👍). We can go ahead and open tickets for them - Also, in reply to your follow-up ticket - we should have separate tickets for them updates like these. |
Sass 1.79 has been released. From the changelog:
Right now this plugin is using the legacy API and the warning is present in the logs due to this sass change. I would like to integrate the proposal done in "Add sass to peerDependencies" with the following points:
I'm available to make this changes after #141 is completed: |
I would like to propose some improvements for this package:
Use
peerDependencies
Add
rollup
topeerDependencies
Since this is a rollup plugin I think this should be added to
peerDependencies
.This will also help to clearly identify which rollup version are supported.
Add
sass
topeerDependencies
I think that user should install separately his
sass
implementation instead of having installed because is included already independencies
.Also, like with rollup, we can clearly identify which version of
sass
are supported, if user install it.Example:
A working example is the
webpack
sass-loader
package.jsonAdd other sass runtime
consider using
webpack-loader
approach so user can install only one sass runtime (right nowsass
will be always be installed since it is a dependency)Code updates
Update source code using async functions and spread operator
I think that code could be updated using async functions in order to reduce callback chain code,
additionally and use modern syntax like spread instead of or
Object.assign
andArray.prototype.concat
.These features are available for
node >= 10
spread
compatibility tableasync
compatibility tableEnable
typescript
strict modePretty self-explanatory 😅
Note
If you are ok with at least one of the proposed changes I can take care of doing separate PR's for each task
This should ease review process a lot!
The text was updated successfully, but these errors were encountered: