way too many deprecated libraries

[Jay-study-nildana]

Folks,

I like the Auth0 samples in general but this one, in particular, has way too many deprecated libraries. some of the libraries are not even maintained anymore.

any chance you might be upgrading this sample soon?

[stevehobbsdev]

👋 We have just updated the sample. It would help if you could identify which libraries in particular that are causing an issue.

[Jay-study-nildana]

hey @stevehobbsdev

I downloaded a fresh sample yesterday. let me run that again and put the error messages here.

Here you go.

npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142

npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142

npm WARN deprecated [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1

npm WARN deprecated [email protected]: this library is no longer supported

npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

npm WARN deprecated [email protected]: use String.prototype.padStart()

npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

I got no complaints, because, it works beautifully. and, the steps are very clear on how i can use it in my own react app (in which case, of course, these errors wont exist because i will be create everything new)

but, sometimes, I want to demo Auth0 to my potential clients, they see this and they get scared. Like, when I trying to upsell Auth0 and they want to see some direct samples and all that.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇‍♂️

[stevehobbsdev]

I'll keep this open and try to update the libraries 👍

[Jay-study-nildana]

@stevehobbsdev

sounds good. its not a hurry situation. the app works just fine except for so many warnings :)

[Jay-study-nildana]

Today, I just realized that its fairly straightforward to update to the latest packages and get rid of most of the errors.

Some errors remain but they have nothing to do with the sample itself.

    $ npx npm-check-updates -u
    $ npm install 

I even added typescript to the Auth0sample, and nothing has broken so far.

@stevehobbsdev you can close this issue. I have solved it and put the notes here in this comment. but if you want to keep it open and do the updates and then close, that is always better, yes. meanwhile, other developers who come here can simply update and solve it on their own.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇‍♂️

[stevehobbsdev]

Keeping this open, will hopefully be resolved by #224

[frederikprijck]

Closing because https://github.com/auth0-samples/auth0-react-samples/pull/224 got merged