NodeJS Paths to Socket.IO Issue

New to NodeJS, having trouble with path description to modules, both server and client side. I'm Node and Linux challenged.

Both server.js and index.html resides at "/opt/mydir/www/workingDirectory/" resides at "/usr/lib/node_modules/" resides at "/usr/lib/node_modules/"

so in server.js :  var socketio = require('./usr/lib/node_modules/');    (not sure is this is correct??)
index.html: <script type="text/javascript" src="./usr/lib/node_modules/"></script>
the path in index.html must be wrong, I'm getting a js error in Firefox console:
"Reference error: io is not defined
var iosocket = io.connect();

any assistance would be appreciated
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dave BaldwinFixer of ProblemsCommented:
I suspect that the dot in './' is your problem because that makes it relative to the current directory.  Remove the dot and use just '/' because those are absolute paths on the server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kevbob650Author Commented:
So I think the path issue is okay now, but still not able to get the server up. constantly getting the "Error: listen EADDRINUSE" no matter what port I specify in listen:
var app = require("/usr/lib/node_modules/express");
var server = require("http").createServer();
var io = require("/usr/lib/node_modules/")(server);


console.log("server running");

io.on("connection", function (socket) {
    var tweet = {user: "nodesource", text: "Hello, world!"};

    // to make things interesting, have it send every second
    var interval = setInterval(function () {
        socket.emit("tweet", tweet);
    }, 1000);

    socket.on("disconnect", function () {
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.