Could dependency "source-map-resolve" be updated to 0.6.0 ? Also, dependency urix is deprecated.

[sr-01-01]

This part of the "npm list" tree:

┬ [email protected]
│ │ ├── [email protected] deduped
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ ├── [email protected]
│ │ │ ├── [email protected]
│ │ │ ├── [email protected]
│ │ │ ├── [email protected]
│ │ │ └── [email protected] deduped
│ │ └── [email protected]

source-map-resolve has a new version (0.6.0) which do not use deprecated urix and resolve-url packages.

[kboedges]

I have a local branch ready to fix both of these if I can get permission to push 🙂

[beeman]

Hey @kboedges that would be great - you can probably already create a PR so that the owner of the repo merges it.

However, from looking at the activity it looks like they lost interest in this project.

[kboedges]

@beeman I think I was attempting to submit a PR incorrectly (new to the open source process). Thanks!

[beeman]

@kboedges feel free to reach out on Twitter if you need a hand, happy to help!

[kboedges]

I think I have it setup correctly 🤞 #140

[beeman]

I think I have it setup correctly 🤞 #140

Yep, that looks great!

[beeman]

Thanks for releasing the new version @SlexAxton! Latest css does not have deprecations anymore!

[garysheppardjr]

It looks like all versions of source-map-resolve are now deprecated. css still depends on it.

[Lonli-Lokli]

@beeman can you upgrade css?

[beeman]

@beeman can you upgrade css?

I wish but I'm not the package owner.

It seems abandoned, last update was two years ago 🤷‍♂️

[Lonli-Lokli]

@fritz-c mb you are the right person ? :)

[holblin]

I worked on removing the source-map support. This will solve the issue. Trying to reach out to the rework members before going into the fork route (and discussing with my company for the PR route).
ref: #164