minimonolith 0.21.0 → 0.21.1

package/README.md

@@ -116,18 +116,18 @@ export default ({ MODELS }) => ({
 
 ## App Environments
 
-There are 4 possible environments: DEV=TRUE & PROD=FALSE, DEV=TRUE & PROD=TRUE, DEV=FALSE & PROD=TRUE, DEV=FALSE & PROD=TRUE
-1. DEV=TRUE & PROD=FALSE: This is the standard DEV environment
-2. DEV=FALSE & PROD=FALSE: This is the standard QA environment
-3. DEV=FALSE & PROD=TRUE: This is the stnadard PROD environment
-4. DEV=TRUE & PROD=TRUE: This allows to test the behavior of PROD within the "new concept" of DEV environment
+There are 4 possible environments:
+1. DEV=TRUE + PROD=FALSE: This is the standard DEV environment
+2. DEV=FALSE + PROD=FALSE: This is the standard QA environment
+3. DEV=FALSE + PROD=TRUE: This is the stnadard PROD environment
+4. DEV=TRUE + PROD=TRUE: This allows to test the behavior of PROD within the "new concept" of DEV environment
 
 To better understand their relevance:
 1. The "new concept" DEV environments (DEV=TRUE) aim to make the api crash if an "important" error happens
   - Its current only difference is it makes it crash on error at service registration phase
   - Some may think QA should also fail on "important" errors They can use DEV=TRUE there But some do training activities on QA that must be minimally disrupted
 2. The "new concept" QA environments (PROD=FALSE) aim at logging data about the system which on production environments would be forbiden personal information
-  1. This is relevant because replication of QA activities (even security QA activities) depend heavily on this
+  - This is relevant because replication of QA activities (even security QA activities) depend heavily on this
 
 The current App environment is determined on the values of MM_API_DEV ENV [TRUE/FALSE] and MM_API_PROD_ENV [TRUE/FALSE]:
 
@@ -138,7 +138,7 @@ MM_API_PROD_ENV=FALSE
 [...]
 ```
 
-*NOTICE*: If this variables are not added to .env/Lambda environment it is assumed standard PROD environment (DEV=FLASE & PROD=TRUE)
+*NOTICE*: If this variables are not added to .env/Lambda environment it is assumed standard PROD environment (DEV=FLASE + PROD=TRUE)
 - This means that sequelize will not alter automatically tables having mismatches with defined model.js files
 - Database dialect/credentials detected will not be printed
 - Critical errors will not make the app crash

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "minimonolith",
   "type": "module",
-  "version": "0.21.0",
+  "version": "0.21.1",
   "main": "index.js",
   "license": "MIT",
   "scripts": {

package/src/development/createDevEnvironment.js

@@ -1,10 +1,10 @@
-import runLambdaServer from './runLambdaServer.js';
+import lambdaServer from './lambdaServer.js';
 
 const createDevEnvironment = async (ENV_FILE='.env', MODULE_FOLDER='node_modules/') => {
   const { loadEnvFile } = await import('./loadEnvFile.js');
   loadEnvFile(ENV_FILE, MODULE_FOLDER);
 
-  return runLambdaServer;
+  return lambdaServer;
 }
 
 export default createDevEnvironment;

package/src/development/lambdaServer.js

@@ -2,10 +2,10 @@ import http from 'http';
 
 import { getServerHandler } from './serverHandler.js';
 
-const runLambdaServer = (lambdaHandler, port) => {
+const lambdaServer = (lambdaHandler, port) => {
   const serverHandler = getServerHandler(lambdaHandler);
   const server = http.createServer(serverHandler);
   server.listen(port);
 }
 
-export { runLambdaServer };
+export default lambdaServer;