Skip to content

Commit

Permalink
fix: Dependency upgrade
Browse files Browse the repository at this point in the history
  • Loading branch information
keonik committed Jul 19, 2023
1 parent 872d6a2 commit 757f57f
Show file tree
Hide file tree
Showing 3 changed files with 22 additions and 17 deletions.
21 changes: 13 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,9 @@
# Prisma Entity Relationship Diagram Generator

<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->

[![All Contributors](https://img.shields.io/badge/all_contributors-17-orange.svg?style=flat-square)](#contributors-)

<!-- ALL-CONTRIBUTORS-BADGE:END -->

Prisma generator to create an ER Diagram every time you generate your prisma client.
Expand Down Expand Up @@ -206,17 +208,19 @@ Because this package relies on [mermaid js](https://mermaid.js.org/) and [puppet

### 🔴 **ARM64 Users** 🔴

Puppeteer does not yet come shipped with a version of Chromium for arm64, so you will need to point to a Chromium executable on your system.
Puppeteer does not yet come shipped with a version of Chromium for arm64, so you will need to point to a Chromium executable on your system.
More details on this issue can be found [here](https://github.com/puppeteer/puppeteer/issues/7740).

**MacOS Fix:**

Install Chromium using Brew:

```bash
brew install --cask --no-quarantine chromium
```

You should now see the path to your installed Chromium.
You should now see the path to your installed Chromium.

```bash
which chromium
```
Expand All @@ -226,12 +230,13 @@ The generator will use this Chromium instead of the one provided by Puppeteer.
**Other Operating Systems:**

This can be fixed by either:
- Setting the `executablePath` property in your puppeteer config file to the file path of the Chromium executable on your system.
- Setting the following global variables on your system
```
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
PUPPETEER_EXECUTABLE_PATH=path_to_your_chromium
```

- Setting the `executablePath` property in your puppeteer config file to the file path of the Chromium executable on your system.
- Setting the following global variables on your system
```
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
PUPPETEER_EXECUTABLE_PATH=path_to_your_chromium
```

## Contributors ✨

Expand Down
16 changes: 8 additions & 8 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@
"jest": "^29.6.1",
"prettier": "3.0.0",
"prisma": "^5.0.0",
"puppeteer": "^20.8.2",
"puppeteer": "^20.8.3",
"semantic-release": "^21.0.7",
"standard-version": "^9.5.0",
"tslib": "^2.6.0",
Expand Down

0 comments on commit 757f57f

Please sign in to comment.