Parse-SDK-JS
Parse-SDK-JS copied to clipboard
refactor: bump UUID dep, remove 'deep require' of uuid
See UUID documentation - https://github.com/uuidjs/uuid#deep-requires-now-deprecated
New Pull Request Checklist
- [X] I am not disclosing a vulnerability.
- [X] I am creating this PR in reference to an issue.
Issue Description
The way Parse requires the uuid package is discouraged by the maintainers, and seems to be causing issues with other dependencies in my project.
Related issue: https://github.com/parse-community/Parse-SDK-JS/issues/1491
Approach
This PR updates the uuid dependency fro 3x to 8x, and modifies the way it is imported/required, to use a named import, instead of the deprecated deep require appraoch.
I am not an expert in the nuances of JS import/require approaches so would appreciate some input from someone on this change -it seems to be sensible to me and in line with what the uuid project maintainers recommend (https://github.com/uuidjs/uuid#deep-requires-now-deprecated).
TODOs before merging
- [ ] Add entry to changelog
Thanks for opening this pull request!
- ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.
I will reformat the title to use the proper commit message syntax.
Could you take a look at the failing tests?
@mtrezza Yes I'll take a look this week (For reference / in case anyone can help - it seems to be a permissions related thing? Not sure if people come across this commonly when commiting to this repo for the first time?)

Maybe rebasing this PR on alpha fixes this, see https://github.com/parse-community/Parse-SDK-JS/pull/1495.
@mtrezza I'll give that a go thank you!
It seems the package-lock file still has a conflict
@mtrezza - taking a look
@mtrezza - I'm seeing this message, could you kindly re-run this workflow?
Did you recreate the package-lock file? 26,671 additions, 165 deletions looks unusual for this simple dependency upgrade.
@jpgupta Could you use the package-lock file from the alpha branch and do the dependency upgrade again?
@mtrezza sorry for the delay, bunch of things going on - will take a look at this in the next few days
Closing for bot to recreate PR.