Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First thing's first, keep it simple. Every new tool you add is another dependency, and another potential stress point for the project. With that in mind, some good tools, methodologies, and best-practices for server-side javascript development are:</p> <p><strong>Folder Structure</strong> This doesn't <em>really</em> matter. Just do what makes sense to you, and what you think will make sense to others if you plan to have collaborators. Search github for Node.JS projects and see how they're structured. I found one good example: <a href="https://github.com/thomasdavis/backbonetutorials/tree/gh-pages/examples/nodejs-mongodb-mongoose-restify" rel="nofollow">https://github.com/thomasdavis/backbonetutorials/tree/gh-pages/examples/nodejs-mongodb-mongoose-restify</a></p> <p><strong>Libraries</strong> The libraries you use is going to greatly depend on what type of project you're working on. Does the REST API hit a database? Is it MongoDB, redis, MySQL, Neo4J, ... ? You're going to need an interface for that. Express is a great framework. (I believe it can start a project for you even.)</p> <p><strong>Technologies</strong> Have you considered Coffee/Clojure-script? This extra step at compile time can save you a lot of headaches later on. Your code will also be more readable to others. Jslint is another great tool to verify javascript code. Also, I have to suggest using git for version control. If you aren't: learn it, master it, use it. <a href="http://www.git-legit.org/" rel="nofollow">http://www.git-legit.org/</a></p> <p><strong>Methods</strong> Your software development strategy will be dependent on what tools you end up using as well as your own personal choices with regard to how you like to write software. I would suggest using Jenkins to continuously integrate your code, and some sort of test framework to ensure what you write is right.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload