From 2af47f6ddae2413e03b89acc0246bcffb2b97a03 Mon Sep 17 00:00:00 2001 From: fredericsoumare Date: Wed, 8 Jul 2020 11:40:05 +0200 Subject: [PATCH] Update RFC section on inter-package dependencies Apply suggestions of https://github.com/emberjs/rfcs/pull/284#issuecomment-601880269 --- text/0000-explode.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/text/0000-explode.md b/text/0000-explode.md index 3f6b834e58..d6fa6ec909 100644 --- a/text/0000-explode.md +++ b/text/0000-explode.md @@ -39,7 +39,9 @@ Even though we expect to have many "breaking" releases of `@ember/core` during t If one of the newly-split-off Ember packages depends on another, it will say so in its NPM peerDependencies. We will use exact-version constraints, which is effectively how things already work today. -NPM has historically been loose about peerDependencies, so they are often ignored by developers. We propose that ember-cli should hard error for missing peerDependencies to avoid this problem (most people who think they don't really need to clean up peerDependency warnings are simply mistaken, and have latent bugs). +NPM has historically been loose about peerDependencies, so they are often ignored by developers. We propose that ember-cli should hard error for missing peerDependencies only in Ember's own packages to avoid this problem (most people who think they don't really need to clean up peerDependency warnings are simply mistaken, and have latent bugs). + +An environment variable will be created to suppress the error so that people who are doing advanced debugging of the ember packages themselves can test scenarios that involve mismatched package versions. ## Addon dependencies on Ember packages