dhiwise/dhiwise-nodejs

DhiWise Node.js API generator allows you to instantly generate secure REST APIs. Just supply your database schema to DhiWise, and a fully documented CRUD APIs will be ready for consumption in a few simple clicks. The generated code is clean, scalable, and customizable.

Node.js Code Generator

Node.js code generator is a developer-centric platform to build backend CRUD APIs along with other essential features to boost developers' productivity time by twofold!

Developers just need to add their schema data to reduce their work related to models into a few simple configurations. Developers can also configure platforms , routes, role access, authentication & more for their application.

Most importantly, the Node.js code generator gives developers total code ownership. The code it generates is bug-free and easily customizable

Table of contents

• Get started

• Supported Architectures

• Features

• Documentation

Get started

After a successful run, a user can configure different settings using UI, and build an app to generate the code.

1. To run npm i && npm run start

⚠️ Note: Use npm i --force If your npm installation fails. As Node version >= 14 will give you errors if peer dependency in different packages have ambiguation in versions.

2. With npm run start project will run on 3000 port.
3. Run http://localhost:3000 and you will see "create application" form. After creating an application you can configure modules and build the app to get the source code.

4. After a successful build, Generated code will resides inside the **packages/server/output** folder.

Supported architectures

This project provides two architectures to choose from, while creating an application.

Clean Code

The main rule of clean architecture is that code dependencies can only move from the outer levels inward. Code on the inner layers can have no knowledge of functions on the outer layers.

MVC - Model-View-Controller

The Model-View-Controller (MVC) is an architectural pattern that separates an application into three main logical components: the model, the view, and the controller. Each of these components are built to handle specific development aspects of an application.

Features of generated code

1. User Authentication and Authorization (using Passport)
2. Social Login APIs
3. CRUD APIs with middleware and attributes' selection
4. List API with pagination, populate and queries
5. Upload attachment API with validation and storage options like (Local server or S3 public/private bucket)
6. Role-Permission
7. Hooks and Indexes
8. Policy/middleware
9. API request body validation (Using joi)
10. API response with standard error and message pattern
11. Test cases
12. Postman collection and API documentation
13. Constants
14. Environment Variables for development, QA and production
15. Custom API setup
16. Multiple Platform selection and User type configuration
17. MVC and Clean-code architecture
18. Supported Databases
    a. MongoDB
    b. SQL Server
    c. MYSQL
    d. PostgreSQL

Documentation

Here's the Documentation of How you can use generated APIs

Contribution

Have you found a bug? 🐞 Please report it here or have a nice feature 💡 to contribute? Add it here
Our Contribution guide will help you how to contribute.

Support

If you have problems or questions go to our Discord channel, we will then try to help you as quickly as possible: https://discord.gg/hTuNauNjyJ

dhiwise-nodejs's Issues

[BUG] Unable to move past onboarding

As the title says :-

1. I signed up, asked me a bunch of questions like company name, role etc.
2. I chose Android as the technology.
3. Asked me import a design, I selected, " I don't have a design" and so it gave me a choice to select Explore or Template.
4. I chose explore, selected 1 screen, pressed '+' and clicked on proceed.
5. On clicking 'Proceed', it said "Application Added Successfully" and then it again goes back to onboarding! Back to step (2) all over again. This seems to be going in an infinite loop.

:rocket: Feature: Add a service layer that contains the business logic in the clean code architecture

problem
The problem with the current architecture is that, all the business logic of APIs are in the controller files. so if I want to use to same logic in any other function then I can't reuse the code. (for eg, same APIs logic for desktop , client and device platforms with minor changes)

solution
The service layer (basically called use cases) that contains business logic so it can be resuable for multiple platforms.

UI hangs and mouse is not responsive

Hello,

I am wondering if anyone else encountered the same issue.

After running npm i && npm run start, a new browser window is opened with a form to create a new app. However, the fields (inputs and all UI buttons) are not responsive to user clicks. To enter for instance the name of the app, I have to use the keyboard Tab to navigate to the "application name" input field. I can then continue using the Tab to navigate to other fields. Even after creating the application, the UI is still not responsive to user clicks (ex: for creating models).

I suspect this may be related to the auto-generated main.css found in packages/client/src/assets/css/main.css. But I can't figure out what the issue is exactly in this file.

I've tested on Chrome and Safari browsers and the issue persists on both.

Any help/advise would be much appreciated!

npm i error

on windows 11 laptop

1. git clone the repo
2. npm run start

Cannot install

Current Behavior:

There are these errors after running npm i :

npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/lerna
npm ERR!   dev lerna@"^4.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer lerna@"^3.0.0" from [email protected]
npm ERR! node_modules/cz-lerna-changelog
npm ERR!   dev cz-lerna-changelog@"^2.0.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Steps To Reproduce:

• Download the code via github
• Run npm i

Environment:

• OS: Windows 10 Enterprise v1909
• Node: 16.14.2
• npm: 8.6.0

[BUG] <title>npm i error

When i start npm i , after clonning repo , i get this error :

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/lerna
npm ERR! dev lerna@"^4.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer lerna@"^3.0.0" from [email protected]
npm ERR! node_modules/cz-lerna-changelog
npm ERR! dev cz-lerna-changelog@"^2.0.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

i am using intel mac , node version v16.15.0 , npm version 8.5.5

[BUG] With latest node version 16.15.0 and npm version 8.5.5 even npm install -- force fails

Current Behavior:

1. Clone this repo
2. did npm install -- force
3. expectation was to successful installing of all packages and project to be ready to run

Expected Behavior:

npm install as well as npm install -- force booth are failing with error.

error with npm install

error with npm install -- force

Environment:

• Node: 16.15.0
• npm: 8.5.5
• windows 10

[BUG] Unable to resolve dependency

Current Behavior:

npm i or yarn cannot resolve the dependency.

Expected Behavior:

Git cloned project should resolve all dependencies.

Steps To Reproduce:

Follow steps outlined here in the docs.

Environment:

Anything else:

Terminal Output of error.

lerna ERR! npm install exited 1 in 'nodejs-code-generator'
lerna ERR! npm install stderr:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: nodejs-code-generator@0.0.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"^17.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.0.0" from react-dropdown-tree-select@0.0.0-semantic-release
npm ERR! node_modules/react-dropdown-tree-select
npm ERR!   react-dropdown-tree-select@"git+https://github.com/DhiWise/react-dropdown-tree-select" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See .../.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     .../.npm/_logs/2022-03-02T17_22_25_113Z-debug-0.log
lerna ERR! npm install exited 1 in 'nodejs-code-generator'
npm ERR! code 1
npm ERR! path .../Downloads/Code/hoa_web_app/dhiwise-nodejs
npm ERR! command failed
npm ERR! command sh -c lerna clean -y && lerna bootstrap --hoist

Will your other generators be available, for example for flutter in opensource ?

Hi, I tested your generator for nodejs, it's pretty cool. We would like to use your other products on our servers, will they be in opensource or on-prem?

[BUG] Infinite Loading in Browser

Current Behavior:

In browser the logo is continiously loading, without making any progress.
I also had to install using npm i --force

Expected Behavior:

Taken to on boarding

Steps To Reproduce:

npm i --force
npm run

In browser console:
`[HMR] Waiting for update signal from WDS...
index.js:1 Warning: Legacy context API has been detected within a strict-mode tree.

The old API will be supported in all 16.x releases, but applications using it should migrate to the new version.

Please update the following components: LoadableComponent

Learn more about this warning here: https://reactjs.org/link/legacy-context
at LoadableComponent (http://localhost:3000/static/js/vendors~main.chunk.js:36350:7)
at Route (http://localhost:3000/static/js/vendors~main.chunk.js:39892:29)
at Switch (http://localhost:3000/static/js/vendors~main.chunk.js:40061:29)
at App
at Router (http://localhost:3000/static/js/vendors~main.chunk.js:39564:30)
at BrowserRouter (http://localhost:3000/static/js/vendors~main.chunk.js:39078:35)
at ToastProvider (http://localhost:3000/static/js/vendors~main.chunk.js:41554:5)
at PersistGate (http://localhost:3000/static/js/vendors~main.chunk.js:54213:5)
at Provider (http://localhost:3000/static/js/vendors~main.chunk.js:36562:20)
at RecoilRoot_INTERNAL (http://localhost:3000/static/js/vendors~main.chunk.js:50220:3)
at RecoilRoot (http://localhost:3000/static/js/vendors~main.chunk.js:50359:5)
at MainApp
at App
console. @ index.js:1
printWarning @ react-dom.development.js:67
error @ react-dom.development.js:43
(anonymous) @ react-dom.development.js:11587
push.../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushLegacyContextWarning @ react-dom.development.js:11571
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23819
commitRootImpl @ react-dom.development.js:23005
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
commitRoot @ react-dom.development.js:22990
performSyncWorkOnRoot @ react-dom.development.js:22329
(anonymous) @ react-dom.development.js:11327
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
flushSyncCallbackQueueImpl @ react-dom.development.js:11322
flushSyncCallbackQueue @ react-dom.development.js:11309
scheduleUpdateOnFiber @ react-dom.development.js:21893
enqueueSetState @ react-dom.development.js:12467
push.../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:365
(anonymous) @ react.js:61
dispatch @ redux.js:297
rehydrate @ persistStore.js:79
_rehydrate @ persistReducer.js:61
(anonymous) @ persistReducer.js:90
Promise.then (async)
(anonymous) @ persistReducer.js:89
Promise.then (async)
(anonymous) @ persistReducer.js:84
dispatch @ redux.js:288
(anonymous) @ serializableStateInvariantMiddleware.ts:210
(anonymous) @ index.js:20
(anonymous) @ immutableStateInvariantMiddleware.ts:266
(anonymous) @ actionCreatorInvariantMiddleware.ts:32
persist @ persistStore.js:114
persistStore @ persistStore.js:123
(anonymous) @ App.js:13
./src/App.js @ App.js:37
webpack_require @ bootstrap:856
fn @ bootstrap:150
(anonymous) @ buildProcessConstant.js:23
./src/index.js @ index.js:21
webpack_require @ bootstrap:856
fn @ bootstrap:150
1 @ reportWebVitals.js:16
webpack_require @ bootstrap:856
checkDeferredModules @ bootstrap:45
webpackJsonpCallback @ bootstrap:32
(anonymous) @ main.chunk.js:1
react-dom.development.js:67 Warning: componentWillMount has been renamed, and is not recommended for use. See https://reactjs.org/link/unsafe-component-lifecycles for details.

• Move code with side effects to componentDidMount, and set initial state in the constructor.
• Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 18.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: LoadableComponent
printWarning @ react-dom.development.js:67
warn @ react-dom.development.js:34
push.../../node_modules/react-dom/cjs/react-dom.development.js.ReactStrictModeWarnings.flushPendingUnsafeLifecycleWarnings @ react-dom.development.js:11524
flushRenderPhaseStrictModeWarningsInDEV @ react-dom.development.js:23822
commitRootImpl @ react-dom.development.js:23005
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
commitRoot @ react-dom.development.js:22990
performSyncWorkOnRoot @ react-dom.development.js:22329
(anonymous) @ react-dom.development.js:11327
unstable_runWithPriority @ scheduler.development.js:468
runWithPriority$1 @ react-dom.development.js:11276
flushSyncCallbackQueueImpl @ react-dom.development.js:11322
flushSyncCallbackQueue @ react-dom.development.js:11309
scheduleUpdateOnFiber @ react-dom.development.js:21893
enqueueSetState @ react-dom.development.js:12467
push.../../node_modules/react/cjs/react.development.js.Component.setState @ react.development.js:365
(anonymous) @ react.js:61
dispatch @ redux.js:297
rehydrate @ persistStore.js:79
_rehydrate @ persistReducer.js:61
(anonymous) @ persistReducer.js:90
Promise.then (async)
(anonymous) @ persistReducer.js:89
Promise.then (async)
(anonymous) @ persistReducer.js:84
dispatch @ redux.js:288
(anonymous) @ serializableStateInvariantMiddleware.ts:210
(anonymous) @ index.js:20
(anonymous) @ immutableStateInvariantMiddleware.ts:266
(anonymous) @ actionCreatorInvariantMiddleware.ts:32
persist @ persistStore.js:114
persistStore @ persistStore.js:123
(anonymous) @ App.js:13
./src/App.js @ App.js:37
webpack_require @ bootstrap:856
fn @ bootstrap:150
(anonymous) @ buildProcessConstant.js:23
./src/index.js @ index.js:21
webpack_require @ bootstrap:856
fn @ bootstrap:150
1 @ reportWebVitals.js:16
webpack_require @ bootstrap:856
checkDeferredModules @ bootstrap:45
webpackJsonpCallback @ bootstrap:32
(anonymous) @ main.chunk.js:1
2index.js:1 /Users/vivienroggero/Documents/source/dhiwise-nodejs/node_modules/@jridgewell/gen-mapping/dist/gen-mapping.mjs
Can't import the named export 'SetArray' from non EcmaScript module (only default export is available)
console. @ index.js:1
handleErrors @ webpackHotDevClient.js:174
push.../../node_modules/react-dev-utils/webpackHotDevClient.js.connection.onmessage @ webpackHotDevClient.js:213
index.js:1 /Users/vivienroggero/Documents/source/dhiwise-nodejs/node_modules/@jridgewell/gen-mapping/dist/gen-mapping.mjs
Can't import the named export 'TraceMap' from non EcmaScript module (only default export is available)
console. @ index.js:1
handleErrors @ webpackHotDevClient.js:174
push.../../node_modules/react-dev-utils/webpackHotDevClient.js.connection.onmessage @ webpackHotDevClient.js:213
index.js:1 /Users/vivienroggero/Documents/source/dhiwise-nodejs/node_modules/@jridgewell/trace-mapping/dist/trace-mapping.mjs
Can't import the named export 'decode' from non EcmaScript module (only default export is available)
console. @ index.js:1
handleErrors @ webpackHotDevClient.js:174
push.../../node_modules/react-dev-utils/webpackHotDevClient.js.connection.onmessage @ webpackHotDevClient.js:213
index.js:1 /Users/vivienroggero/Documents/source/dhiwise-nodejs/node_modules/@jridgewell/gen-mapping/dist/gen-mapping.mjs
Can't import the named export 'decodedMappings' from non EcmaScript module (only default export is available)
console. @ index.js:1
handleErrors @ webpackHotDevClient.js:174
push.../../node_modules/react-dev-utils/webpackHotDevClient.js.connection.onmessage @ webpackHotDevClient.js:213
index.js:1 /Users/vivienroggero/Documents/source/dhiwise-nodejs/node_modules/@jridgewell/trace-mapping/dist/trace-mapping.mjs
Can't import the named export 'encode' from non EcmaScript module (only default export is available)
console. @ index.js:1
handleErrors @ webpackHotDevClient.js:174
push.../../node_modules/react-dev-utils/webpackHotDevClient.js.connection.onmessage @ webpackHotDevClient.js:213
index.js:1 /Users/vivienroggero/Documents/source/dhiwise-nodejs/node_modules/@jridgewell/gen-mapping/dist/gen-mapping.mjs
Can't import the named export 'encode' from non EcmaScript module (only default export is available)
console. @ index.js:1
handleErrors @ webpackHotDevClient.js:174
push.../../node_modules/react-dev-utils/webpackHotDevClient.js.connection.onmessage @ webpackHotDevClient.js:213
4index.js:1 /Users/vivienroggero/Documents/source/dhiwise-nodejs/node_modules/@jridgewell/gen-mapping/dist/gen-mapping.mjs
Can't import the named export 'put' from non EcmaScript module (only default export is available)
console. @ index.js:1
handleErrors @ webpackHotDevClient.js:174
push.../../node_modules/react-dev-utils/webpackHotDevClient.js.connection.onmessage @ webpackHotDevClient.js:213
index.js:1 /Users/vivienroggero/Documents/source/dhiwise-nodejs/node_modules/@monaco-editor/react/dist/index.mjs 124:62
Module parse failed: Unexpected token (124:62)
File was processed with these loaders:

• ../../node_modules/babel-loader/lib/index.js
  You may need an additional loader to handle the result of these loaders.
  | k(() => {
  | let i = Se.init();

return i.then(f => (c.current = f) && s(!1)).catch(f => f?.type !== "cancelation" && console.error("Monaco initialization: error:", f)), () => u.current ? I() : i.cancel();

| }), l(() => {
| if (u.current && c.current) {
console. @ index.js:1
handleErrors @ webpackHotDevClient.js:174
push.../../node_modules/react-dev-utils/webpackHotDevClient.js.connection.onmessage @ webpackHotDevClient.js:213
VM260:2 Uncaught ReferenceError: process is not defined
at 4043 (:2:13168)
at r (:2:306599)
at 8048 (:2:9496)
at r (:2:306599)
at 8641 (:2:1379)
at r (:2:306599)
at :2:315627
at :2:324225
at :2:324229
at e.onload (index.js:1:1)`

Environment:

• OS: Mac os Ventura 13.0
• Node: v16.15.1
• npm: 9.8.1

[BUG] npm run dont work

Current Behavior:

doing npm i && npm run start error

Expected Behavior:

its need to run as expected on the readme file

Steps To Reproduce:

error when trying to run npm run start

Current Behavior:

When I try to run the project
npm i && npm run start

Error:
found 18 vulnerabilities (12 moderate, 6 high)
  run `npm audit fix` to fix them, or `npm audit` for details

> [email protected] start /Users/agustin/Dev/dhiwise-nodejs
> lerna run start

lerna notice cli v4.0.0
lerna info Executing command in 2 packages: "npm run start"
lerna ERR! npm run start exited 1 in '@nodejs-code-generator/server'
lerna ERR! npm run start stdout:

> @nodejs-code-generator/[email protected] start /Users/agustin/Dev/dhiwise-nodejs/packages/server
> node --inspect=0.0.0.0 app.js

lerna ERR! npm run start stderr:
Debugger listening on ws://0.0.0.0:9229/f8808c4b-4b93-41e3-bc08-4a54878e4c48
For help, see: https://nodejs.org/en/docs/inspector
/Users/agustin/Dev/dhiwise-nodejs/packages/server/models/Repo/index.js:19
    if (result?.error) {
               ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/Users/agustin/Dev/dhiwise-nodejs/packages/server/repo/project.js:2:31)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/Users/agustin/Dev/dhiwise-nodejs/packages/server/controllers/web/project/index.js:1:27)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @nodejs-code-generator/[email protected] start: `node --inspect=0.0.0.0 app.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @nodejs-code-generator/[email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/agustin/.npm/_logs/2022-01-27T02_19_52_924Z-debug.log
lerna ERR! npm run start exited 1 in '@nodejs-code-generator/server'
lerna WARN complete Waiting for 1 child process to exit. CTRL-C to exit immediately.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `lerna run start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/agustin/.npm/_logs/2022-01-27T02_19_52_967Z-debug.log

Environment:

macos m1
node 12.22.7

:hammer: API Code Refactor

Description
API code refactor and new Authentication Flow with Platform, Comments, loggedInUser route and more.

:bug: Bug: Installtion failed due to internal jsonlint access

Steps To Reproduce:

npm install

Environment:

• OS: Windows 10
• Node: 14.17.3
• npm: 6.14.13

Error

npm ERR! Error while executing: npm ERR! C:\Program Files\Git\cmd\git.EXE ls-remote -h -t https://github.com/DhiWise/jsonlint.git npm ERR! npm ERR! fatal: unable to access 'https://github.com/DhiWise/jsonlint.git/': SSL certificate problem: self signed certificate in certificate chain npm ERR! npm ERR! exited with error code: 128

Note

It seems npm installtion is trying to pull repo from github. This will fail as organization firewall will block. Ideally repo should use jsonlint via package file

:rocket: Feature: Overwrite the application in storage if the application has more than one build

problem
When an application has more than one build, it creates a new application directory every time. so the changes of every build come in the new directory.

solution
Overwrite the current build with new changes, give a warning about it, and add nodemon in the start script so that the new build can restart the local server with new changes.