Error cannot find module socket io

Cannot find module socket.io #11

I am getting the error in the title when I run docker-compose up
I have installed socket.io after running docker-compose run chat bash and rebuilt it even with —no-cache option. And I can require(‘socket.io’) inside the machine’s node console.

The text was updated successfully, but these errors were encountered:

Hi, sorry I haven’t responded sooner. It seems likely that the node_modules aren’t installed inside the container, for some reason, but I don’t think there’s enough information here for me to provide any more specific advice, unfortunately.

Hi @jdleesmiller
First of all I would like to sincerely thank you for this tutorial.
I’ve been trying to figure out the right way to start developing a nodeJS app from scratch using only docker and this is the most clear and best explained description of the whole process that one could ask for.
Once said that I have to say that I found myself stuck for a while in this same issue (that’s why I am not opening a new one).

To install socket.io I run:
$ docker-compose run —rm chat /bin/bash
chat$ npm install —save socket.io
After that socket.io is in my package.json as well as in the chat/node_modules folder.
But running $ docker-compose up after rebuilding (even with —no-cache) always results in :

Attaching to docker-chat-demo_chat_1
chat_1 | module.js:327
chat_1 | throw err;
chat_1 | ^
chat_1 |
chat_1 | Error: Cannot find module ‘socket.io’
chat_1 | at Function.Module._resolveFilename (module.js:325:15)
chat_1 | at Function.Module._load (module.js:276:25)
chat_1 | at Module.require (module.js:353:17)
chat_1 | at require (internal/module.js:12:17)
chat_1 | at Object. (/home/app/chat/index.js:3:10)
chat_1 | at Module._compile (module.js:409:26)
chat_1 | at Object.Module._extensions..js (module.js:416:10)
chat_1 | at Module.load (module.js:343:32)
chat_1 | at Function.Module._load (module.js:300:12)
chat_1 | at Function.Module.runMain (module.js:441:10)

After some googling and stackoverflowing I tried to install socket.io globally through the Dockerfile but the result was exactly the same.
I managed to make it (kind of)work by following the next workaround:
$ docker-compose run —rm chat /bin/bash
chat$ node index.js
Once I do that I get the *listening on :3000 and I can open the chat in the browser and it works as expected.
I understand that if it works with this workaround it means that socket.io is where is supposed to be and also that the syntax in the index.js is fine.
Can you help me to understand what is going on here and why does it not work with docker-compose up?
(of course my code looks exactly the same as in https://github.com/jdleesmiller/docker-chat-demo/tree/04-the-app)

Thanks for getting in touch. I would guess that it is somehow using a cached version of the node_modules volume that does not have the socket.io package installed. Does it help if you run

(the -v tells docker-compose to remove the volumes as well as the container)

Or, failing that

which should destroy all containers and volumes and then bring them back.

Источник

socket.io-client module not found #2801

Note: for support questions, please use one of these channels: stackoverflow or slack

You want to:

• report a bug
• request a feature

Current behaviour

I built a simple task list with this and was able to get it to work a few months ago. I am going back to build another more robust program, but am getting this error when I try to run webpack 1.13.1:
ERROR in ./socket-listeners/task-listener.js
Module not found: Error: Cannot resolve module ‘socket.io-client’ in /home/ubuntu/workspace/socket-listeners
@ ./socket-listeners/task-listener.js 33:9-36

Steps to reproduce (if the current behaviour is a bug)

I have used both «import io from ‘socket.io-client’;» and «const io = require(‘socket.io-client’);» and both reproduce the same error.

Expected behaviour

I was expecting it to find the module on its own. I am able to find it manually in my node_modules folder.

Setup

• OS: not sure if this counts as I use Cloud 9. I tried to work it on my local machine using windows 10, but experienced the same result.
• browser: chrome
• socket.io version: 1.4.8

I’m hoping this can be fixed relatively quickly as this is going to be a final project so I can graduate. If anybody has any work-around, please let me know. Thanks!

The text was updated successfully, but these errors were encountered:

How did you install the package? Could you share your webpack config?

The package.json nor bower.json are configured properly

@killerspaz would you know what can be improved / fixed?

Thanks, @killerspaz. That’s what did the trick, just had to dig a little deeper into the socket.io module:
import io from ‘socket.io/node_modules/socket.io-client’;

@darrachequesne sorry, my feedback was actually meant for socket.io-client , not this project. Must have gotten switched up somehow. Upon further inspection, it looks like bower.json is missing, and written as .bower.json , but with invalid data? I’m not fully understanding what’s going on there, since bower says it’s grabbing from https://github.com/LearnBoost/socket.io-client.git, which my URL is redirecting to https://github.com/socketio/socket.io-client.git; but the source certainly doesn’t appear to have this file. Apparently bower adds it. Utilizing debowerify fails somewhere along the line saying it can’t find socket.io-client . I ended up referencing socket.io-client/dist/socket.io for it to resolve properly.

@jstrother, you can use just socket.io-client to reduce packages if you wanted. It’s not really optimal or suggested to dig into a module’s dependencies.

As with @killerspaz I needed to reference socket.io-client/dist/socket.io

Thanks, @killerspaz, that worked. (Sorry for being late responding)

error: Error: Unable to resolve module use-socket.io-client from App.js : use-socket.io-client could not be found within the project.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Error: Cannot find module ‘engine.io’ — chat example #1581

I have just cloned socket.io repository and tried to run example (from within socket.io/examples/chat directory) by following instructions in readme file. Unfortunately after running node . i get this message:

The same thing is happend on osx and freebsd.

I am quite new to node, so it`s possible that i have omitted something.

The text was updated successfully, but these errors were encountered:

@pawski it sounds like either the npm install step is missing, or was unsuccessful. If you run npm install in the example directory, what do you see?

@rase- Here is the output:

@pawski The issue is that the example app doesn’t actually depend on socket.io, but uses the relative parent. In the main socket.io git repo you also have to run npm install and that should fix the missing dependency error. Good luck! We can probably close this issue now.

@kevin-roark Great! It works. Thank You.

Could you add to readme that the npm install needs to be run at the root folder first, I was confused too.

This is very simple to solve.
In your examples/chat folder, open the index.js file and change these lines of code.

before
Var io = require (‘../ ..’) (server);

after
Var io = require (‘socket.io’) (server);

And that’s it, it’s working!
You do not need to run npm in the main folder.

@Williaan Great man its solved

I am facing same issue. Please help..
npm install output:

Источник

Requiring unknown module «socket.io-client/socket.io» #48

First, thanks for releasing such a wonderful tool. I decided to give it a go in the project we are building. I upgrade to version RN 23 first without issues, then I added to App.js which is used by both platform indexes:

This goes before configuring the redux store. However I’m getting this red screen:

The moment I remove those 3 previous lines everything works again.

Thanks, cheers
Miguel

The text was updated successfully, but these errors were encountered:

How did you install? npm i reactotron —save-dev ?

It sounds like the dependency on socket.io failed to be installed properly.

Looks like you’re on Android too. Try another react-native run-android .

One other thing, you’ve got two connect() calls. You only need one. Try nuking the first one.

Lemme know how it goes.

That’s right, I installed it with —save-dev argument, If I list node_modules directory inside reactotron I get:

Nothing about socket.io , which I’m guessing smells.

Yes, I’m in Android too, I’ve recompiled several times, but it’s not fixing the issue. I removed the first connect, but that didn’t help either.

Thanks for your super fast answer!
Miguel

Woah. ya, that’s not right.

What happens if you type npm install socket.io —save from your project? can you install it explicitly?

I just tried to install socket.io with your command and it did work:

I’m surprised too, if you have it listed in your package.json it should be installed, I’m gonna check if I can upgrade my npm.

Here’s my setup (osx 10.11.4 & brew-based node)

Well. socket.io-client is a dependency for socket.io . Prior npm 3 , modules’ dependencies were not available to all other modules and sub-modules. Not even the main project!

I use nvm, and I’ve installed node v5.10.1 as you have, also with npm 3.8.6. I delete my node_modules and reinstall everything. Apparently since version 3 of npm dependencies are flatten in node_modules directory. However after doing so, I hit random packager bugs reported in RN. Specially this one:

Unable to find prelude_dev.js file, although it’s there. The transformation process of the packager hangs there without finishing, similar to facebook/react-native#2949

When I use npm 2.15.3 with node v4.1.1 the packager is able to transform my project but I end up with the socket.io-client/socket.io unknown module.

To be honest, I’m not sure what can I do to upgrade versions of node and npm without having issues. But I now believe that reactotron needs npm version 3 or newer.

Thanks guys. For npm 2.x, I wonder if it is simply required to add dependencies for socket.io’s dependencies too? Seems odd. I’ll look at other packages for socket.io and see what they do.

@maraujop — what happens if you remove reactotron from the equation? Does it work? Is it something in this module that is triggering this problem?

I just pushed 0.6.1 which now supports Node 4.x and npm 2.x.

Would you mind giving that a go @maraujop ?

Thank you kindly!

I can confirm the bug fix did work. I’ve just installed 0.6.1 with npm 2 and it no longer prompts a red screen, great! I’m so excited to see reactotron working 🙂

About when I use npm 3, I believe in that case it is another module the one that triggers the issue, however it will be hard to find, like find a needle in haystack.

I’m closing the issue and thanks for your great support again,
Miguel

Источник

Click here follow the steps to fix Node.js Error Cannot Find Module ‘socket.io’ and related errors.

Instructions

Note:
This article was updated on 2023-02-03 and previously published under WIKI_Q210794

What is Node.js Error Cannot Find Module ‘socket.io’ error?

The Node.js Error Cannot Find Module ‘socket.io’ error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors.

This code is used by the vendor to identify the error caused. This Node.js Error Cannot Find Module ‘socket.io’ error code has a numeric error number and a technical description. In some cases the error may have more parameters in Node.js Error Cannot Find Module ‘socket.io’ format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error.

What causes Node.js Error Cannot Find Module ‘socket.io’ error?

The Node.js Error Cannot Find Module ‘socket.io’ error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer.

There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware
attack or by an improper shutdown of the computer. All the above actives
may result in the deletion or corruption of the entries in the windows
system files. This corrupted system file will lead to the missing and wrongly
linked information and files needed for the proper working of the
application.

How to easily fix Node.js Error Cannot Find Module ‘socket.io’ error?

There are two (2) ways to fix Node.js Error Cannot Find Module ‘socket.io’ Error:

Advanced Computer User Solution (manual update):

1) Start your computer and log on as an administrator.

2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.

3) In the new window, select «Restore my computer to an earlier time» option and then click Next.

4) Select the most recent system restore point from the «On this list, click a restore point» list, and then click Next.

5) Click Next on the confirmation window.

6) Restarts the computer when the restoration is finished.

Novice Computer User Solution (completely automated):

1) Download (Node.js Error Cannot Find Module ‘socket.io’) repair utility.

2) Install program and click Scan button.

3) Click the Fix Errors button when scan is completed.

4) Restart your computer.

How does it work?

This tool will scan and diagnose, then repairs, your PC with patent
pending technology that fix your windows operating system registry
structure.
basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.)

[~]# node node.js

Error: Cannot find module 'socket.io'

[~]# node -v
v0.10.10

npm install socket.io

npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field

8 Answers

var io = require('../lib/socket.io');

sudo npm install socket.io

/home/.../.npm/socket.io

/usr/local/lib/node_modules/socket.io

npm install socket.io --save

 < script type="text/javascript" src="/socket.io/socket.io.js"></script>

var io = require('socket.io').listen(server);

{
  "compilerOptions": {
    ....
    "moduleResolution": "node",
  }
}