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

update all website packages to latest version #1380

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 9 additions & 7 deletions docs/LocalDevelopment.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@ Our recommended workflow is to use [`yarn link`][1] to register local `metro` pa
From inside our `metro` clone, `yarn link` is responsible for registering local package folders to be linked to elsewhere.

We recommend using `npm exec --workspaces` to register all packages in the `metro` repo — these can be individually linked into the target project later.

npm exec --workspaces -- yarn link

```sh
npm exec --workspaces -- yarn link
```
2. **Use `yarn link` to replace Metro packages in your target project**

From inside our target project folder, `yarn link <package-name>` can be used to apply our registered `metro` packages for that project only.
Expand Down Expand Up @@ -59,7 +59,9 @@ Our recommended workflow is to use [`yarn link`][1] to register local `metro` pa

Now we should be able to run Metro within our target project. Remember to restart this command after any code changes you make to `metro` or to the target project's `metro.config.js` file.

yarn react-native start
```sh
yarn react-native start
```

4. **(Optional) Clean up with `yarn unlink`**

Expand All @@ -70,7 +72,7 @@ Our recommended workflow is to use [`yarn link`][1] to register local `metro` pa
Metro uses the [debug](https://www.npmjs.com/package/debug) package to write logs under named debug scopes (for example: `Metro:WatchmanWatcher`). Set the `DEBUG` environment variable before starting Metro to enable logs matching the supplied pattern.

The snippet below provides a pattern matching all Metro-defined messages.

DEBUG='Metro:*' yarn metro serve

```sh
DEBUG='Metro:*' yarn metro serve
```
[1]: https://classic.yarnpkg.com/en/docs/cli/link
7 changes: 6 additions & 1 deletion website/docusaurus.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,12 @@ const siteConfig = {
indexName: 'metro',
},
prism: {
additionalLanguages: ['flow'],
additionalLanguages: [
'flow',
'bash',
'json',
'diff',
],
},
},
scripts: ['https://buttons.github.io/buttons.js'],
Expand Down
32 changes: 14 additions & 18 deletions website/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -12,25 +12,21 @@
"serve": "docusaurus serve"
},
"dependencies": {
"@docusaurus/core": "2.4.3",
"@docusaurus/preset-classic": "2.4.3",
"classnames": "2.2.6",
"docusaurus-plugin-internaldocs-fb": "1.18.5",
"docusaurus-plugin-sass": "^0.2.1",
"react": "17.0.2",
"react-dom": "17.0.2",
"react-github-btn": "1.1.1",
"sass": "^1.46.0"
"@docusaurus/core": "3.6.0",
"@docusaurus/preset-classic": "3.6.0",
"@mdx-js/react": "^3.1.0",
"classnames": "2.5.1",
"docusaurus-plugin-internaldocs-fb": "1.19.0",
"docusaurus-plugin-sass": "^0.2.5",
"prism-react-renderer": "^2.4.0",
"react": "18.3.1",
"react-dom": "18.3.1",
"react-github-btn": "1.4.0",
"sass": "^1.80.6"
},
"devDependencies": {
"@docusaurus/module-type-aliases": "2.4.3",
"prettier": "2.8.8"
},
"resolutions": {
"@sideway/formula": "^3.0.1",
"got": "^11.8.5",
"http-cache-semantics": "^4.1.1",
"terser": "^5.14.2",
"trim": "^0.0.3"
"@docusaurus/module-type-aliases": "3.6.0",
"@docusaurus/types": "3.6.0",
"prettier": "3.3.3"
}
}
Loading
Loading