From c2496bfa3cdb5ba4a49afb1953e1d48b032632c1 Mon Sep 17 00:00:00 2001 From: Eli Perelman Date: Mon, 27 Mar 2017 18:10:15 -0500 Subject: [PATCH] Middleware vs. Presets? (#149) --- docs/FAQ.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/FAQ.md b/docs/FAQ.md index 0d41bae..222315a 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -67,3 +67,12 @@ object that corresponds with this "schema". Typically this would involve transfo entities requiring a name into an object which maps the name to the entity. In short, you must transform your Webpack configuration in order to merge it into the Neutrino configuration cleanly. + +### What is the difference between middleware and presets? + +The term "presets" are a hold-over from Neutrino pre-v5. Presets **are** middleware, the difference in reality is in +name only. To keep the term "presets" relevant, we typically want to use it when referring to major project types: +React projects, Node.js projects, composite middleware (conglomeration of many middleware), etc. + +The takeaway: most middleware can just be middleware, and use the term preset for major project types or +composite middleware.