search

datatypevoid / vulgar

A simple and scalable MEAN stack development kit featuring Angular 2 (Router, Http, Forms, Services, Tests, E2E, Coverage, Dev/Prod), Express, MongoDB, Mongoose, Node, PassportJS, Socket.io, Karma, Protractor, Jasmine, Istanbul, SASS Support, TypeScript, TSLint, NG2Lint, Hot Module Replacement, Docco, Gulp, and Webpack by @datatypevoid
MIT License
286 stars 66 forks source link

after init and npm install, npm run build errors #4

Closed cmwhited1990 closed 8 years ago

cmwhited1990 commented 8 years ago

Note: for support questions, please use one of these channels: Chat: VulgarDisplayOf2^2.slack or Twitter: @datatype_void

npm-debug-log.txt vulgar cli snapshot

[X ] bug report

[ ] feature request

[ ] question about the decisions made in the repository

Following along with the vulgar-cli quick start. -Ran the npm install -g vulgar-cli generator-vulgar. -Ran vulgar init -cd -npm install -npm run build --> THIS THROWS ERROR -- Error starts at "Cannot find module './config.json' -- Please see included image and npm debug log

ENVIRONMENT: -node.js version 5.10.1 -npm version 3.8.6 -Windows 7 x64

datatypevoid commented 8 years ago

Hmm, I will have to take a look. As far as I know it should run fine. Can you check to see if it generated config/config.json?

cmwhited1990 commented 8 years ago

it did not generate config/config.json

datatypevoid commented 8 years ago

I'll take a look later when I get off of work. I'll let you know what I uncover!

cmwhited1990 commented 8 years ago

Thanks. I appreciate it.

datatypevoid commented 8 years ago

No problem. If you want to try and get around this for now, you can insert this object into config/config.json and run vulgar init again: 

{
  "ENV" : "development",
  "PORT" : 3000,
  "MONGO_URI" : {
    "DEVELOPMENT" : "mongodb://localhost:27017/vulgar-dev",
    "PRODUCTION" : "mongodb://localhost:27017/vulgar-prod",
    "TEST" : "mongodb://localhost:27017/vulgar-test"
  },
  "SESSION_SECRET" : "355FC4FE9348639B4E4FED1B8E93C"
}

That should bypass this particular error hopefully.

datatypevoid commented 8 years ago

Standard installation works fine for me on multiple Win10 x64 boxes as well as a Ubuntu 14.04 box. Have you had any progress on your end?