Skip to content
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

chore: remove i18next and react-dom as direct dependencies #3138

Merged
merged 2 commits into from
Oct 29, 2024

Conversation

jenniferarnesen
Copy link
Collaborator

@jenniferarnesen jenniferarnesen commented Oct 29, 2024

  • i18next gets installed as a dependency of d2-i18n, so it doesn't need to be a direct dependency in the app
  • react-dom gets installed as a dependency of app-shell. And it was only used directly for testing. In the tests it has been replaced by a testing library. One useless test was removed.

@dhis2-bot
Copy link
Contributor

dhis2-bot commented Oct 29, 2024

🚀 Deployed on https://pr-3138.dashboard.netlify.dhis2.org

@dhis2-bot dhis2-bot temporarily deployed to netlify October 29, 2024 10:00 Inactive
@dhis2-bot dhis2-bot temporarily deployed to netlify October 29, 2024 10:22 Inactive
@jenniferarnesen jenniferarnesen changed the title chore: remove i18next as direct dependency chore: remove i18next and react-dom as direct dependencies Oct 29, 2024
@jenniferarnesen jenniferarnesen merged commit 5083e6a into master Oct 29, 2024
32 checks passed
@jenniferarnesen jenniferarnesen deleted the chore/remove-i18next-dependency branch October 29, 2024 12:48
jenniferarnesen added a commit that referenced this pull request Oct 29, 2024
* i18next gets installed as a dependency of d2-i18n,
so it doesn't need to be a direct dependency in the app

* react-dom gets installed as a dependency of app-shell. And it was only
used directly for testing. In the tests it has been replaced by a testing library.
One useless test was removed.
jenniferarnesen added a commit that referenced this pull request Oct 29, 2024
* chore(deps): bump the security group with 4 updates

Updates `express` from 4.19.2 to 4.21.1
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/4.21.1/History.md)
- [Commits](expressjs/express@4.19.2...4.21.1)

Updates `path-to-regexp` from 0.1.7 to 0.1.10
- [Release notes](https://github.com/pillarjs/path-to-regexp/releases)
- [Changelog](https://github.com/pillarjs/path-to-regexp/blob/master/History.md)
- [Commits](pillarjs/path-to-regexp@v0.1.7...v0.1.10)

Updates `send` from 0.18.0 to 0.19.0
- [Release notes](https://github.com/pillarjs/send/releases)
- [Changelog](https://github.com/pillarjs/send/blob/master/HISTORY.md)
- [Commits](pillarjs/send@0.18.0...0.19.0)

Updates `serve-static` from 1.15.0 to 1.16.2
- [Release notes](https://github.com/expressjs/serve-static/releases)
- [Changelog](https://github.com/expressjs/serve-static/blob/v1.16.2/HISTORY.md)
- [Commits](expressjs/serve-static@v1.15.0...v1.16.2)

---
updated-dependencies:
- dependency-name: express
  dependency-type: indirect
  dependency-group: security
- dependency-name: path-to-regexp
  dependency-type: indirect
  dependency-group: security
- dependency-name: send
  dependency-type: indirect
  dependency-group: security
- dependency-name: serve-static
  dependency-type: indirect
  dependency-group: security
...

Signed-off-by: dependabot[bot] <support@github.com>

* chore: remove i18next and react-dom as direct dependencies (#3138)

* i18next gets installed as a dependency of d2-i18n,
so it doesn't need to be a direct dependency in the app

* react-dom gets installed as a dependency of app-shell. And it was only
used directly for testing. In the tests it has been replaced by a testing library.
One useless test was removed.

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Jen Jones Arnesen <jennifer@dhis2.org>
@dhis2-bot
Copy link
Contributor

🎉 This PR is included in version 100.3.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants