-
Notifications
You must be signed in to change notification settings - Fork 76
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
Express 4 support #161
Comments
If you set "express" version to "latest" in your project package.json dependencies then NPM will install version 4.9.0 — at the time this was written. I don't see in what Nodeclipse is concerned by any node module's version as this is mostly a coding issue to me: if your app need Express 4.x.x then install Express 4.x.x with NPM. |
I have Express 4.x.x installed but when you create a New Project with Nodeclipse, it creates an Express 3.2.6 project. { There are big differences between Express 3.x.x and 4.x.x that need to be changed in the JavaScript as can be seen when you use express-generator (4.x.x) to create a project (which won’t run under Nodeclipse). |
Yes - Express 4 is not using connect middleware anymore: http://expressjs.com/migrating-4.html When you create a new Express 4 project from express-generator it's not a Nodeclipse project - therefore it won't run as node application from Nodeclipse... But it didn't run either from a terminal for me here...
Node exits without any output — am I missing something important in this process? Running it as Node application from Nodeclipse node.js process is just terminated: Which is not a surprise as it's not a Nodeclipse project (no project resources - etc): in my understanding an Express 4 project would need to be generated by Nodeclipse to be run from Nodeclipse — as a new project type. |
You have to start it with “npm start”. |
If you look at package.json, you will see how it starts now: { "dependencies": { |
Interesting: what about NPMEclipse then ;+) |
works too: { |
To summarize, we now have two different issues: |
Yes, and that is what you have to put in the Run Configuration to make it work in Eclipse. |
I think that will do it. You might want to add the ability to choose between a 3.x and 4.x in the creation process. |
How do you set Run Configuration to make it run? |
Choose New Configuration, then click Search: … and start typing “w” and it pops up the matching values: … choose which folder in “In folders” by double-clicking on it. Or, you can just type in the path i.e. /searchPiper/bin/www |
This doesn’t always work. I have had apps running for hours and then killed them and they won’t restart. |
<?xml version="1.0" encoding="UTF-8"?> It's not a Nodeclipse project: <buildSpec> and <natures> elements are empty — so I don't see how it could run in Nodeclipse... |
It has run for me on numerous occasions. It created a .project: myPiper org.nodeclipse.ui.NodeNature org.eclipse.wst.jsdt.core.jsNature |
So, mine has quit running again. I can’t figure out under what conditions it stops and, more frustrating, what makes it start working again. It is not a complete reboot and it is not creating a New Configuration nor is it starting it in the command line, stopping it, and coming back to Eclipse. When it is running, it is good for several days, typically, before it stops again. |
as Patrick @nodeleaf said we now have two different issues:
any other questions, please create an issue per question |
Express version in NodePreferencesPage
Is there support for Express 4.x.x in Nodeclipse?
The text was updated successfully, but these errors were encountered: