[Proposal] yarn to npm

[yuki0410-dev]

Description: I suggest moving from yarn to npm.

Linked issue: -

Problem

• Some PACKAGES cannot be added or removed because they use yarn v1.
  • Warning: pattern is trying to unpack in the same destination yarnpkg/yarn#4812
  • https://github.com/Hacker0x01/react-datepicker/blob/114f06adfdaee028e3442438cc9bb7c97199be32/docs-site/package.json#L39C6-L39C16

Changes

• Migrated package manager from yarn to npm.
  • Fixed Github Actions.
• Removed unnecessary packages that were blocked due to yarn v1.
• Organized the naming of npm scripts since there was no regularity in naming them.

Contribution checklist

• I have followed the contributing guidelines.
• I have added sufficient test coverage for my changes.
• I have formatted my code with Prettier and checked for linting issues with ESLint for code readability.

[pullrequest]

⚠️ This pull request was not sent to the PullRequest network because the pull request is a draft.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.39%. Comparing base (c550195) to head (84d808f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4904   +/-   ##
=======================================
  Coverage   96.39%   96.39%           
=======================================
  Files          28       28           
  Lines        3305     3305           
  Branches     1387     1400   +13     
=======================================
  Hits         3186     3186           
+ Misses        119      115    -4     
- Partials        0        4    +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pullrequest]

✅ This pull request was sent to the PullRequest network for review. Expert reviewers are now being matched to your request based on the code's requirements. Stay tuned!

What to expect from this code review:

• Comments posted to any areas of potential concern or improvement.
• Detailed feedback or actions needed to resolve issues that are found.
• Turnaround times vary, but we aim to be swift.

---

@yuki0410-dev you can click here to see the review status or cancel the code review job.

[pullrequest]

PullRequest Breakdown

Reviewable lines of change

+ 84
- 110

31% GitHubActions
23% JSON
22% Markdown
18% GitHubActions (tests)
6% Other

Generated lines of change

+ 92,081
- 26,420

Type of change

Feature - These changes are adding a new feature or improvement to existing code.

[yuki0410-dev]

Since type check by tsc is already performed at the time of rollup build and at the time of ts-jest execution, it is not necessary to perform it again here.

[pullrequest]

On its own, this change looks fine sans a formatting nit. However, changing from yarn to npm is a fairly significant change to be occurring without previous consensus on doing so. Personally, I don't see the need for it, particularly as there is a workaround that is already being used. However this decision is up to the HackerOne team.

Jacob

---

Reviewed with ❤️ by PullRequest

[pullrequest]

No issues found in this change, looks good to me.

Jacques

---

Reviewed with ❤️ by PullRequest

[yuki0410-dev]

However, changing from yarn to npm is a fairly significant change to be occurring without previous consensus on doing so.

I agree.
I created the PR as a suggestion, hoping that you would be able to judge from the specific changes!

Personally, I don't see the need for it, particularly as there is a workaround that is already being used.

There are some PACKAGES that cannot be deleted due to the use of YARN.
#4896

I have not had any problems at all with npm.

However this decision is up to the HackerOne team.

I think you are right.

[yuki0410-dev]

@martijnrusschen
What do you think about this change?
We are willing to resolve conflicts if the policy seems acceptable.

[pullrequest]

PullRequest reviewed the updates made to #4904 since our last review was posted. This includes comments that have been posted by non-PullRequest reviewers. No further issues were found.

Reviewed by:

Jacques

[yuki0410-dev]

@martijnrusschen
Would it be possible to merge this PR conflict if I fix it?

[pullrequest]

I see no issues with this change, looks good to me!

Jacques

---

Reviewed with ❤️ by PullRequest

[pullrequest]

Due to inactivity, PullRequest has cancelled this review job. You can reactivate the code review job from the PullRequest dashboard.