-
Notifications
You must be signed in to change notification settings - Fork 259
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
Typescript support, performance optimization and browser friendly version (no source-map) #164
Comments
A PR is generally the recommended route for this |
Yes, but the changes are quite important, so before smashing a PR that changes the whole setup, dependencies, and so on I prefer to have a discussion if possible (and that allows me to start discussing while I get agreement from my company). On top of that, it seems that the member of the rework are currently not very responsive, so I already thinking about creating a fork if I can't get a response. Lastly, even if I get a PR merged, it's not guaranteed that they will do an npm release ( #151 (comment) ) 👀 |
Here is the fork I created: https://github.com/adobe/css-tools |
@holblin Cool. Maybe you can hit up angular team to use your package instead of reworkcss. |
Great package @holblin , thank you so much. |
Hi,
I use
css
for multiple of our projects and I have an issue with the source-map support.Indeed, due to Webpack 5 and some projects that can't eject from create-react-app, these teams couldn't use CSS (fs can't be polyfilled because Webpack config is not available if you don't eject.).
To solve the issue, I started to fork the project locally and remove the source-map support.
While doing that work I also rewrote some parts of it, moving the project to Typescript and increasing the performance by about 30% in some cases.
How could I contact you (member of rework) to discuss about importing the changes?
@dead-horse @fengmk2 @joakimbeng @jxson @kevva @SlexAxton @tj
The text was updated successfully, but these errors were encountered: