Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update ? #2

Open
fas3r opened this issue Sep 2, 2018 · 13 comments
Open

update ? #2

fas3r opened this issue Sep 2, 2018 · 13 comments

Comments

@fas3r
Copy link

fas3r commented Sep 2, 2018

Hello,

following your update in march, do you know when you will publish your new version ?

Thanks.

@kelyvin
Copy link
Owner

kelyvin commented Sep 3, 2018

Hi @fas3r,

Sorry for the delay. My open source & side projects have fallen behind because I've been wrapped up with other priorities. I'm going to try to recommit several hours on Sunday's to play some catch up. With that said, at this point I feel pretty good about the updated architecture (since I've been working in it extensively for the past four months). I just need clean it up to make it more digestable for others. I need to update a different project first today, so I may be able to get to this probably not the next Sunday, but the Sunday after.

Eta-ish around the end of the month? Please check back again if I don't post an update by then.

Thanks!

@fas3r
Copy link
Author

fas3r commented Sep 3, 2018

Hello @kelyvin ,

Thanks for your feedback. Sure I will check that you can be sure, I just wanted to know if it would come alive :).

Thanks !

@henrikra
Copy link

henrikra commented Sep 8, 2018

This is great news! @kelyvin

@ghost
Copy link

ghost commented Sep 25, 2018

Hello m8, i've just cloned your project and tried to start it with npm but it seems that there is an error.

λ npm start

> [email protected] start C:\laragon\www\express-env-example
> node index.js

module.js:538
    throw err;
    ^

Error: Cannot find module 'express-handlebars'
    at Function.Module._resolveFilename (module.js:536:15)
    at Function.Module._load (module.js:466:25)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (C:\laragon\www\express-env-example\server\index.js:5:25)
    at Module._compile (module.js:635:30)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
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!     C:\Users\Natan\AppData\Roaming\npm-cache\_logs\2018-09-25T13_38_01_218Z-debug.log

Do you know where it can come from and how to resolve it ?

@kelyvin
Copy link
Owner

kelyvin commented Sep 26, 2018

@Natizyskunk Have you tried running npm install first to install all your dependencies?

In order to run any Node.js app you'll need to make sure your dependencies are installed before running it. Usually to overcome this I tend to include an install command as part of npm start, but since this was an example project I didn't do it here. Let me know if that addresses your issue

@ghost
Copy link

ghost commented Sep 27, 2018

My bad i should have known that this doesn't work this way and that i needed to do the npm install command before anything else ^^.
It has definitely resolve my problems, thx :)

@eddiemonge
Copy link

How is the update going?

@kelyvin
Copy link
Owner

kelyvin commented Dec 10, 2018

Sorry I totally dropped the ball on this. You've all been very patient.

I have blocked time off my calendar to get to it this week. My new goal is to have the code ready by the end of this month. Thanks for waiting and I'd like to ask if you can hold out just a tad bit longer. I promise the code will have some advanced stuff!

@malek-itani
Copy link

hello @kelyvin ,
thanks for structuring the server in a great way!
i have a question, when you are going to add graphql
so that server supports both ( router and graphql )

@JVGH
Copy link

JVGH commented Mar 2, 2019

Hi kelyvin, this is a great guide for newbs. Thank you! Did you get a chance to update this repo?

@kelyvin
Copy link
Owner

kelyvin commented Mar 7, 2019

Hi @malek-itani - Sorry for not responding, didn't see this message. I don't have any immediate plans to add graphql support, but if I do I'll be sure to let you know.

Hi @JVGH - Thanks for the kind words. Unfortunately, I've been unable to update this repo as I've been focused on other priorities right now. As a result, I've taken a temporary hiatus from my projects/blog. Hopefully, I'll be able to get to it sometime in the year when my main priorities have relaxed a bit, but that won't be for a while. :(

For everyone else, if you have any questions or would like any other tips to help improve your express setup (middleware, environment management, etc), please feel free to ask - answering questions and providing small blocks of code is no problem at all.

@nuri-engin
Copy link

@kelyvin Hello and thanks for that great work!

Wondering if any new update will show up and if it will! Is there any chance to see a way of handling DB connection with that very well handled project?

A usage sample for the MongoDB or any other equivalent DB. Thus achieve a better architect with DB actions etc?

Thanks in advance.

@slidenerd
Copy link

so what is the status now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants