-
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
[email protected] dependency is deprecated #163
Comments
According to |
I also came across this issue, but as a result of an upgrade to webpack 5. Webpack 5 no longer polyfills the |
@pcart-grandjean Definitely agree there should be a more current approach taken given the points he makes. |
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). |
lib/stringify/source-map-support.js seems to be only file that uses If not maybe we can directly use to code by creating a simple js file in this project itself with required code. Pretty sure it can further optimized(e.g, by running coverage, minimize, etc.)
Sry about the long code snippet(this one's about 240 lines). |
From what I saw, it's not used anywhere else. For our purpose, we don't need source-map files so I directly strip those. I will post my changes as soon as I got the green light from my company. Adding back the source map code shouldn't be too hard then but I will personally let other people do it ;-) |
@holblin Any news on this?! |
Yes, we have fork the repository and it's also published into npmjs. |
Thanks for that, sounds great, happy holidays :-) |
The version |
This solves the issue of having outdated and potential insecure transitive dependencies. There are no known behavior changes, so this is considered a non-breaking change / fix. See: reworkcss/css#163 See: SamVerschueren/decode-uri-component#6
This solves the issue of having outdated and potential insecure transitive dependencies. There are no known behavior changes, so this is considered a non-breaking change / fix. See: reworkcss/css#163 See: SamVerschueren/decode-uri-component#6
This solves the issue of having outdated and potential insecure transitive dependencies. There are no known behavior changes, so this is considered a non-breaking change / fix. See: reworkcss/css#163 See: SamVerschueren/decode-uri-component#6
This had been first attempted in 0abe66a but later reverted by 3b6c459 due to adobe/css-tools#77, reapplying since the issue is now fixed. --- This solves the issue of having outdated and potential insecure transitive dependencies. There are no known behavior changes, so this is considered a non-breaking change / fix. See: reworkcss/css#163 See: SamVerschueren/decode-uri-component#6
This had been first attempted in 0abe66a but later reverted by 3b6c459 due to adobe/css-tools#77, reapplying since the issue is now fixed. --- This solves the issue of having outdated and potential insecure transitive dependencies. There are no known behavior changes, so this is considered a non-breaking change / fix. See: reworkcss/css#163 See: SamVerschueren/decode-uri-component#6
a year later, what's the status of this? |
Apparently simply use @adobe/css-tools instead. |
What are you trying to do?
I'm getting warning "npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated ". This warning is from the dependencies "stylus" of package "@angular-devkit/build-angular".
Will it be fix in next release?
What troubleshooting steps have you tried?
Warning comes in production build or during "npm install"
npm i
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
Reproduction
Steps to reproduce:
npm i
Environment
Angular:
CDK/Material:
Browser(s):
Operating System (e.g. Windows, macOS, Ubuntu):
The text was updated successfully, but these errors were encountered: