refactor: dependency upgrades (release)

README.md

@@ -92,30 +92,6 @@ yarn dev
 
 ### Unlinking UI-C
 
-1. In the Bloom directory, run `yarn unlink:uic`.
-2. Open the next.config.js file in the public and partner's directory.
-3. Comment out the experimental property at the bottom of each file.
-4. Follow the directions above to run Bloom locally.
-   Bloom will now be consuming the published version of @bloom-housing/ui-components specified in package.json and no local ui-component changes will be reflected.
-
-### Bloom's UI-Component Development
-
-- Because Bloom's ui-components package is a separate open source repository, developing within both repos locally requires linking the folders with the following steps:
-
-### Directory Setup
-
-1. Clone both Bloom and the [ui-components repository](https://github.com/bloom-housing/ui-components) on the same directory level.
-
-### Symlinking UI-C
-
-1. In the Bloom directory, run `yarn link:uic`.
-2. Open the next.config.js file in the public and partner's directory.
-3. Uncomment the experimental property at the bottom of each file.
-4. Follow the directions above to run Bloom locally.
-   These steps allow for two development patterns. You can edit ui-components within the node_modules of Bloom and the changes will be reflected in your local version of ui-components. Alternatively, you can edit the local version of ui-components and the changes will be reflected in the node_modules in Bloom. Both patterns will display up-to-date changes on the local server.
-
-### Unlinking UI-C
-
 1. In the Bloom directory, run `yarn unlink:uic`.
 2. Open the next.config.js file in the public and partner's directory.
 3. Comment out the experimental property at the bottom of each file.
@@ -130,13 +106,11 @@ Contributions to the core Bloom applications and services are welcomed. To help
 
 Our development tasks are managed through GitHub issues and development in the vast majority of cases should be tied to an issue. Please feel free to submit issues even if you don't plan on implementing it yourself. Before creating an issue, check first to see if one already exists. When creating an issue, give it a descriptive title and include screenshots if relevant. Please don't start work on an issue without checking in with the Bloom team first as it may already be in development! You can tag us (@seanmalbert, @emilyjablonski, @yazeedloonat) to get started on an issue or ask any questions.
 
-### Committing, Versioning, and Releasing
-
-We are using [lerna](https://lerna.js.org/) as a monorepo management tool. It automatically versions, releases, and generates a changelog across our packages. In conjunction with lerna we are also using [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/), a specification for commit messages that helps lerna understand what level of change each commit is in order to automate our processes.
+### Committing
 
-On commit, two steps automatically run: (1) linting and (2) a verification of the conventional commit standard. We recommend not running `git commit` and instead globally installing commitizen (`npm install -g commitizen`) and then committing with `git cz` which will run a commit message CLI. The CLI asks a series of questions about your changeset and builds the commit message for you in the conventional commit format. You can also `git commit` with your own message if you are confident it follows the conventional standard.
+We are also using [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/), a specification for commit messages that indicates what type and level of change each commit is.
 
-In addition to commits needing to be formatted as conventional commits, if you are making different levels of version change across multiple packages, your commits must also be separated by package in order to avoid improperly versioning a package.
+On commit, two steps automatically run: (1) linting and (2) a verification of the conventional commit standard. You can either, instead of running `git commit`, globally install commitizen (`npm install -g commitizen`) and then commit with `git cz` which will run a commit message CLI. The CLI asks a series of questions about your changeset and builds the commit message for you in the conventional commit format. You can alternatively run `git commit` with your own message if you are confident it follows the conventional standard, and it will fail if it does not.
 
 On every merge to `main`, our Netlify and Heroku environment automatically deploys.
 

api/.gitignore

@@ -9,7 +9,6 @@ npm-debug.log*
 pnpm-debug.log*
 yarn-debug.log*
 yarn-error.log*
-lerna-debug.log*
 
 # OS
 .DS_Store

api/package.json

@@ -33,32 +33,36 @@
     "setup:dev": "yarn install && yarn prisma generate && yarn build && yarn db:setup"
   },
   "dependencies": {
-    "@google-cloud/translate": "^7.2.1",
-    "@nestjs/axios": "~3.0.0",
-    "@nestjs/common": "^10.3.2",
-    "@nestjs/config": "~3.0.0",
-    "@nestjs/core": "^10.3.2",
-    "@nestjs/jwt": "~10.1.0",
-    "@nestjs/passport": "~10.0.1",
-    "@nestjs/platform-express": "^10.3.2",
-    "@nestjs/schedule": "^4.0.1",
-    "@nestjs/swagger": "~7.1.12",
+    "@google-cloud/translate": "^8.5.0",
+    "@nestjs/axios": "^3.0.3",
+    "@nestjs/common": "^10.4.4",
+    "@nestjs/config": "^3.2.3",
+    "@nestjs/core": "^10.4.4",
+    "@nestjs/jwt": "^10.2.0",
+    "@nestjs/passport": "^10.0.3",
+    "@nestjs/platform-express": "^10.4.4",
+    "@nestjs/schedule": "^4.1.1",
+    "@nestjs/swagger": "^7.4.2",
     "@nestjs/throttler": "^5.1.2",
     "@prisma/client": "^5.0.0",
+    "@sendgrid/helpers": "^8.0.0",
     "@sendgrid/mail": "7.7.0",
     "@turf/boolean-point-in-polygon": "6.5.0",
     "@turf/buffer": "6.5.0",
     "@turf/helpers": "6.5.0",
     "@turf/points-within-polygon": "6.5.0",
     "@types/archiver": "^6.0.2",
     "archiver": "^6.0.1",
+    "axios": "^1.7.7",
     "casbin": "^5.27.1",
     "class-transformer": "~0.5.1",
     "class-validator": "~0.14.0",
     "cloudinary": "^1.37.3",
     "compression": "^1.7.4",
     "cookie-parser": "~1.4.6",
+    "cron": "^3.1.7",
     "dayjs": "~1.11.9",
+    "dotenv": "^16.4.5",
     "exceljs": "^4.4.0",
     "handlebars": "~4.7.8",
     "jsonwebtoken": "~9.0.1",
@@ -76,9 +80,9 @@
     "twilio": "^4.15.0"
   },
   "devDependencies": {
-    "@nestjs/cli": "^10.3.2",
-    "@nestjs/schematics": "^10.1.1",
-    "@nestjs/testing": "^10.3.2",
+    "@nestjs/cli": "^10.4.5",
+    "@nestjs/schematics": "^10.1.4",
+    "@nestjs/testing": "^10.4.4",
     "@types/compression": "^1.7.5",
     "@types/exceljs": "1.3.0",
     "@types/express": "~4.17.17",
@@ -90,17 +94,17 @@
     "eslint": "^8.0.1",
     "eslint-config-prettier": "^8.3.0",
     "eslint-plugin-prettier": "^4.0.0",
+    "express": "^4.21.1",
     "jest": "~29.6.2",
-    "jest-environment-jsdom": "~29.6.2",
-    "jest-mock-extended": "2.0.4",
+    "jest-mock-extended": "^3.0.7",
     "prettier": "^2.3.2",
-    "source-map-support": "~0.5.20",
     "supertest": "^6.1.3",
     "ts-jest": "~29.1.1",
     "ts-loader": "^9.2.3",
     "ts-node": "^10.0.0",
     "tsconfig-paths": "^3.10.1",
-    "typescript": "^5.1.6"
+    "typescript": "^5.1.6",
+    "webpack": "^5.95.0"
   },
   "jest": {
     "moduleFileExtensions": [