Skip to content

Commit

Permalink
chore: remove unused deps (#7906)
Browse files Browse the repository at this point in the history
* chore: remove unused debounce

* chore: remove unused webpack

chore: remove unused worker-loader

chore: update readme to exclude webpack issues

chore: remove unused regenerator

chore: remove unused puppeteer

chore: remove nocache

chore: remove @types/jsonfile
  • Loading branch information
KenLSM authored Nov 22, 2024
1 parent 07aabd3 commit 4557467
Show file tree
Hide file tree
Showing 7 changed files with 293 additions and 4,158 deletions.
2 changes: 0 additions & 2 deletions __tests__/integration/helpers/express-setup.ts
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@ import compression from 'compression'
import cookieParser from 'cookie-parser'
import express, { Express, Router } from 'express'
import session from 'express-session'
import nocache from 'nocache'

import { errorHandlerMiddlewares } from 'src/app/loaders/express/error-handler'
import helmetMiddlewares from 'src/app/loaders/express/helmet'
Expand Down Expand Up @@ -37,7 +36,6 @@ export const setupApp = (
app.use(compression())
app.use(parserMiddlewares())
app.use(helmetMiddlewares())
app.use(nocache())

app.use(testSessionMiddlewares())

Expand Down
13 changes: 0 additions & 13 deletions docs/TROUBLESHOOTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,19 +41,6 @@ conf.members[0].host = 'database:27017'
rs.reconfig(conf, {force:true})
```

## `TypeError: Cannot read property 'tap' of undefined`

If you are using a machine with an M1 chip, you may be facing this issue due to your `node` installation, as an inappropriate version of `node` would cause more updated versions of `webpack` to be installed and thus introduces breaking changes in the code.

To overcome this, use Rosetta to install `node` in -x86_64 architecture as described in the "Macs with M1 chip" section [here](https://github.com/nvm-sh/nvm#macos-troubleshooting).

Be sure to check that the correct `node` is installed with:

```bash
$ node -p process.arch
x64
```

## `npm` not found

Make sure `nvm` is loaded to the environment in `~/.bash_profile`. To do so, the `~/.bash_profile` should include the following lines:
Expand Down
Loading

0 comments on commit 4557467

Please sign in to comment.