From 257ea6a0ec17c39aafcd106cb0e92906b1678478 Mon Sep 17 00:00:00 2001 From: Jan Piotrowski Date: Fri, 10 Jul 2020 17:04:18 +0200 Subject: [PATCH] chore(website): Fix indentation of "In conclusion" for dependency info (#1204) --- website/content/05-meta/04-architecture.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/05-meta/04-architecture.mdx b/website/content/05-meta/04-architecture.mdx index 95fba5dda..aa1df95b6 100644 --- a/website/content/05-meta/04-architecture.mdx +++ b/website/content/05-meta/04-architecture.mdx @@ -160,7 +160,7 @@ Nexus takes a batteries included approach. Aside from being featureful, it also Of course by doing this you're going outside what a given version of Nexus officially supports, so, YMMV "your mileage may vary"! But its not like if Nexus were using peer dep ranges that this caveat would magically go away. - In conclusion, from both a DX and engineering resource perspective we believe the best dep strategy for Nexus is not peer deps but internalized deps. Recapping the tradeoffs: +In conclusion, from both a DX and engineering resource perspective we believe the best dep strategy for Nexus is not peer deps but internalized deps. Recapping the tradeoffs: - **Cost:** Giving you less flexibility to tailor the packages you use ...but even then _not really_. You _can_ have final say via Yarn's `resolutions` setting.