From 0f2b013b93fbeef90f4160fb533f3a4be7ff91b2 Mon Sep 17 00:00:00 2001 From: Tommy Parnell Date: Wed, 13 Oct 2021 18:03:28 -0400 Subject: [PATCH] fix copy --- .../Posts/Optimizing-Heroku-Cache-For-JS-Monorepos.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/TerribleDev.Blog.Web/Posts/Optimizing-Heroku-Cache-For-JS-Monorepos.md b/src/TerribleDev.Blog.Web/Posts/Optimizing-Heroku-Cache-For-JS-Monorepos.md index 69f4985..c0db712 100644 --- a/src/TerribleDev.Blog.Web/Posts/Optimizing-Heroku-Cache-For-JS-Monorepos.md +++ b/src/TerribleDev.Blog.Web/Posts/Optimizing-Heroku-Cache-For-JS-Monorepos.md @@ -23,7 +23,7 @@ root/ utils ``` -In my quick example we can pretend that an express app in in server, and some background workers are in workers. However both apps need to share code. One stratergy would be to version `data`, and `utils`, or we could use these mono-repo technologies so that `import utils from 'utils'` just works without the need for complex orchestration of packages. However when resolving node modules the following can occur +In my quick example we can pretend that an express app in in server, and some background workers are in workers. However both apps need to share code. One strategy would be to version the `data`, and `utils`, packages and ship them to a private NPM registry, or we could use these mono-repo technologies so that `import utils from 'utils'` just works without the need for a remote package store. When installing node modules into a JS workspace the following can occur ```