From 1d8d7947981ce6f098a3c1272e792db7ba9d9bd0 Mon Sep 17 00:00:00 2001 From: Mike Perry Y Attara <31483629+mikeattara@users.noreply.github.com> Date: Sat, 22 Dec 2018 05:25:52 +0000 Subject: [PATCH 1/4] Update available-scripts.md add the reason for adding packages as dependencies --- docusaurus/docs/available-scripts.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docusaurus/docs/available-scripts.md b/docusaurus/docs/available-scripts.md index f7adadb0853..486241ddaf1 100644 --- a/docusaurus/docs/available-scripts.md +++ b/docusaurus/docs/available-scripts.md @@ -30,6 +30,9 @@ Your app is ready to be deployed! See the section about [deployment](deployment. If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project. -Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own. +Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project as dependencies in `package.json`. Technically, the distinction between dependencies and development dependencies is pretty arbitrary for front-end apps that produce static bundles. +In addition, it used to cause problems for some Heroku deployments that didn't install development dependencies (and thus weren't able to build the project on the server or test it right before deployment). + +However, you have full control over them and can always rearrange `package.json` as you deem reasonable. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own. You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it. From bd9c3f8ff916cdbd65a1a589346b151598ce8c09 Mon Sep 17 00:00:00 2001 From: Amy Lam Date: Wed, 3 Apr 2019 11:12:33 -0700 Subject: [PATCH 2/4] Update available-scripts.md --- docusaurus/docs/available-scripts.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docusaurus/docs/available-scripts.md b/docusaurus/docs/available-scripts.md index 486241ddaf1..9224ef84de3 100644 --- a/docusaurus/docs/available-scripts.md +++ b/docusaurus/docs/available-scripts.md @@ -31,7 +31,8 @@ Your app is ready to be deployed! See the section about [deployment](deployment. If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project. Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project as dependencies in `package.json`. Technically, the distinction between dependencies and development dependencies is pretty arbitrary for front-end apps that produce static bundles. -In addition, it used to cause problems for some Heroku deployments that didn't install development dependencies (and thus weren't able to build the project on the server or test it right before deployment). + +In addition, it used to cause problems with some hosting platforms that didn't install development dependencies (and thus weren't able to build the project on the server or test it right before deployment). However, you have full control over them and can always rearrange `package.json` as you deem reasonable. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own. From 07f116f10db52fc651f6ff4c72d4e86482a6517f Mon Sep 17 00:00:00 2001 From: Amy Lam Date: Wed, 3 Apr 2019 11:33:11 -0700 Subject: [PATCH 3/4] Update available-scripts.md --- docusaurus/docs/available-scripts.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docusaurus/docs/available-scripts.md b/docusaurus/docs/available-scripts.md index 9224ef84de3..4ad478cc617 100644 --- a/docusaurus/docs/available-scripts.md +++ b/docusaurus/docs/available-scripts.md @@ -30,10 +30,10 @@ Your app is ready to be deployed! See the section about [deployment](deployment. If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project. -Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project as dependencies in `package.json`. Technically, the distinction between dependencies and development dependencies is pretty arbitrary for front-end apps that produce static bundles. +Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc.) right into your project as dependencies in `package.json`. Technically, the distinction between dependencies and development dependencies is pretty arbitrary for front-end apps that produce static bundles. -In addition, it used to cause problems with some hosting platforms that didn't install development dependencies (and thus weren't able to build the project on the server or test it right before deployment). +In addition, it used to cause problems with some hosting platforms that didn't install development dependencies (and thus weren't able to build the project on the server or test it right before deployment). You are free to rearrange `package.json` as you see fit. -However, you have full control over them and can always rearrange `package.json` as you deem reasonable. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own. +All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own. You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it. From 0799d21db335c597b39357a18ea8655b607bda5d Mon Sep 17 00:00:00 2001 From: Ian Sutherland Date: Wed, 3 Apr 2019 13:46:39 -0600 Subject: [PATCH 4/4] Update available-scripts.md --- docusaurus/docs/available-scripts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docusaurus/docs/available-scripts.md b/docusaurus/docs/available-scripts.md index 4ad478cc617..b171147528d 100644 --- a/docusaurus/docs/available-scripts.md +++ b/docusaurus/docs/available-scripts.md @@ -30,9 +30,9 @@ Your app is ready to be deployed! See the section about [deployment](deployment. If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project. -Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc.) right into your project as dependencies in `package.json`. Technically, the distinction between dependencies and development dependencies is pretty arbitrary for front-end apps that produce static bundles. +Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc.) into your project as dependencies in `package.json`. Technically, the distinction between dependencies and development dependencies is pretty arbitrary for front-end apps that produce static bundles. -In addition, it used to cause problems with some hosting platforms that didn't install development dependencies (and thus weren't able to build the project on the server or test it right before deployment). You are free to rearrange `package.json` as you see fit. +In addition, it used to cause problems with some hosting platforms that didn't install development dependencies (and thus weren't able to build the project on the server or test it right before deployment). You are free to rearrange your dependencies in `package.json` as you see fit. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.