From bb90f1f17861654ce5dcc1a4b6c7bc2037a9b852 Mon Sep 17 00:00:00 2001 From: mattsjones Date: Wed, 27 Feb 2019 08:23:33 +1100 Subject: [PATCH] docs: Suggest compile package in library docs (#327) --- docs/docs/libraries.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/docs/libraries.md b/docs/docs/libraries.md index eca016be0..3216874ac 100644 --- a/docs/docs/libraries.md +++ b/docs/docs/libraries.md @@ -2,6 +2,8 @@ If you need to build a UMD library instead of a web site, you can provide a `libraryEntry` and `libraryName` option instead: +> If you are creating a package to share between multiple sku apps, then you probably want [compile packages](./docs/extra-features#compile-packages) instead. Libraries should only be used when you have very little control over the target environment (e.g. legacy applications, externally hosted solutions like Auth0). + ```js modules.exports = { libraryEntry: 'src/library.js',