-
Notifications
You must be signed in to change notification settings - Fork 117
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
README update about gulp4 #365
Comments
@nmccready Specifically it's the option |
10-4, well maybe I will dig in an finish my PR for switching css processing to postcss. |
@nmccready the goal is to move any extra features out the namespaced |
Does this mean you guys have no intention to fix this issue with the |
I am still working on that PR, I will be resuming it today. If I wasn't the issue would be closed. |
@nmccready Ah ok, thank you. Wasn't sure but yes that makes sense. Thanks. |
I am going to close this issue as I don't see sourcemaps fully evolving unless someone spear heads the source mapping at gulp. @phated is there a new figure head which is rolling in to take the burden off your shoulders since you're more of a Reason man now? |
I think this is worthy to keep open. We have an issue at #285 that gathers the requirements needed for deprecating. I'll try to come up with a concise, yet detailed explanation for the README. |
@phated can you modify the main README.md with information about sourcemaps being rolled into the core of gulp4. I feel you fill out this info the best.
This is one the main reasons this library has stopped being updated. This is the main reason why css updates have not been done yet.
But I guess this could help those that are stuck on gulp3. Then again my time is limited.
The text was updated successfully, but these errors were encountered: