README update about gulp4

[nmccready]

@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.

[benjclark]

@nmccready
I have discovered that there is still value in maintaining aspects of gulp-sourcemaps even though Gulp 4 now provides sourcemaps functionality.

Specifically it's the option loadmaps: true. That is not present in Gulp 4, therefore we still need to use a package like this to leverage existing sourcemaps in build steps. An example of this is in a build step that revisions files in production. That build step needs to leverage the sourcemaps created in a previous js (or scss) compilation build step. From what I can tell this cannot be done in Gulp 4 but can be done using this package.

[nmccready]

10-4, well maybe I will dig in an finish my PR for switching css processing to postcss.

[phated]

@nmccready the goal is to move any extra features out the namespaced @gulpsourcemaps modules like I had been doing. Once all those extra features are deferred, the main module will be a direct copy of what gulp uses and then it can be deprecated. I have literally zero time to keep moving on that but if you are making changes, they should happen in a namespaced module and pulled in like the other modules.

[benjclark]

Does this mean you guys have no intention to fix this issue with the loadmaps option (#363)? Please let me know as if so I'll move our organisation on to a different solution. Thanks.

[nmccready]

Does this mean you guys have no intention to fix this issue with the loadmaps option (#363)? Please let me know as if so I'll move our organisation on to a different solution. Thanks.

I am still working on that PR, I will be resuming it today.

If I wasn't the issue would be closed.

[benjclark]

@nmccready Ah ok, thank you. Wasn't sure but yes that makes sense. Thanks.

[nmccready]

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?

[phated]

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.