		@@ -5,6 +5,13 @@ // Route Dependencies

		// Import Model

		// Routes ----------------------------

		// Example:
		// router.get('/:id', function(req, res) {
		// Logic Goes Here
		//})

		// ------------------------------------

		module.exports = router;

index.js

		@@ -14,3 +14,3 @@ #!/usr/bin/env node
		program
		.version('0.0.1')
		.version('0.0.2')
		.option('new <apiName>', 'Generate New Node API.')
		@@ -17,0 +17,0 @@ .option('controller <controllerName>', 'Generate Controller file.')

package.json

		{
		"name": "nopi.js",
		"version": "0.0.1",
		"description": "CLI for generating Node APIs",
		"version": "0.0.2",
		"description": "CLI Tool/Framework for generating Node APIs and Files",
		"main": "index.js",
		@@ -6,0 +6,0 @@ "keywords": [

README.md

		# nopi
		### Nopi is a CLI Tool for generating a simple Node API.
		### Nopi is a CLI Tool / Framework for generating a simple Node API and Files.

		![](nopi.png)
		___
		@@ -23,3 +24,3 @@ ### Installation

		Once it is done, cd to project and start the server with:
		Once it is done, cd to API and start the server with:

		@@ -44,3 +45,3 @@ ```$ npm start```

		Controllers which are generated should be added to the ```index.js``` to connect and route with intended endpoint. Once the controller is setup inside of the index controller, it is connected to your API.
		Controllers which are generated should be added to the ```index.js``` to connect and route with intended endpoint. Once the controller is setup inside of the index controller, it is connected to your API server.

		@@ -47,0 +48,0 @@ Nopi also creates ```.nopiPath``` folder in your project and saves the path of the file type generated. This is to optimize the speed of file creation. By saving this path Nopi does not have to dynamically find the folder again after each generated file.

nopi.js - npm Package Compare versions

New alerts