From 3aac8c59848046fb427aab4373a7aadd7069a24c Mon Sep 17 00:00:00 2001 From: Strek Date: Sun, 22 May 2022 11:06:07 +0530 Subject: [PATCH] use proper code block (#4671) --- beta/src/pages/blog/2019/10/22/react-release-channels.md | 4 ++-- content/blog/2019-10-22-react-release-channels.md | 4 ++-- content/docs/add-react-to-a-website.md | 2 +- content/docs/release-channels.md | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/beta/src/pages/blog/2019/10/22/react-release-channels.md b/beta/src/pages/blog/2019/10/22/react-release-channels.md index bdd4c10b..1bc33e8b 100644 --- a/beta/src/pages/blog/2019/10/22/react-release-channels.md +++ b/beta/src/pages/blog/2019/10/22/react-release-channels.md @@ -58,13 +58,13 @@ If you're the author of a third party React framework, library, developer tool, - Set up a cron job using your preferred continuous integration platform. Cron jobs are supported by both [CircleCI](https://circleci.com/docs/2.0/triggers/#scheduled-builds) and [Travis CI](https://docs.travis-ci.com/user/cron-jobs/). - In the cron job, update your React packages to the most recent React release in the Next channel, using `next` tag on npm. Using the npm cli: - ``` + ```console npm update react@next react-dom@next ``` Or yarn: - ``` + ```console yarn upgrade react@next react-dom@next ``` diff --git a/content/blog/2019-10-22-react-release-channels.md b/content/blog/2019-10-22-react-release-channels.md index cb2f1851..2b65f752 100644 --- a/content/blog/2019-10-22-react-release-channels.md +++ b/content/blog/2019-10-22-react-release-channels.md @@ -58,13 +58,13 @@ If you're the author of a third party React framework, library, developer tool, - Set up a cron job using your preferred continuous integration platform. Cron jobs are supported by both [CircleCI](https://circleci.com/docs/2.0/triggers/#scheduled-builds) and [Travis CI](https://docs.travis-ci.com/user/cron-jobs/). - In the cron job, update your React packages to the most recent React release in the Next channel, using `next` tag on npm. Using the npm cli: - ``` + ```console npm update react@next react-dom@next ``` Or yarn: - ``` + ```console yarn upgrade react@next react-dom@next ``` - Run your test suite against the updated packages. diff --git a/content/docs/add-react-to-a-website.md b/content/docs/add-react-to-a-website.md index 07c49475..d842556f 100644 --- a/content/docs/add-react-to-a-website.md +++ b/content/docs/add-react-to-a-website.md @@ -184,7 +184,7 @@ Congratulations! You just added a **production-ready JSX setup** to your project Create a folder called `src` and run this terminal command: -``` +```console npx babel --watch src --out-dir . --presets react-app/prod ``` diff --git a/content/docs/release-channels.md b/content/docs/release-channels.md index b71d55a6..aa05985e 100644 --- a/content/docs/release-channels.md +++ b/content/docs/release-channels.md @@ -53,13 +53,13 @@ If you're the author of a third party React framework, library, developer tool, - Set up a cron job using your preferred continuous integration platform. Cron jobs are supported by both [CircleCI](https://circleci.com/docs/2.0/triggers/#scheduled-builds) and [Travis CI](https://docs.travis-ci.com/user/cron-jobs/). - In the cron job, update your React packages to the most recent React release in the Next channel, using `next` tag on npm. Using the npm cli: - ``` + ```console npm update react@next react-dom@next ``` Or yarn: - ``` + ```console yarn upgrade react@next react-dom@next ``` - Run your test suite against the updated packages.