loopbackio / loopbackio/loopback-next
Not able to run @loopback/socketio example
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.1k
- Forks
- 1.1k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 27
Description
### Describe the bug
I am not able to run socket io example end to end
1. I tried via cli example it though error which is attached in logs
2. manually created same example but it throws cors error
3. example doesn't have rest & socketio combined example
**_Can you please give me running example of loopback 4 socket io which contains rest api as well?_**
### Logs
```shell
lb4 example
? What example would you like to clone? socketio
✖ An error occured while running loopback4:example#downloadAndExtract
(node:3894) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, rename '/Users/saurabhmanchanda/Documents/Work/Personal/loopback4-example-socketio/tsconfig.build.json' -> '/Users/saurabhmanchanda/Documents/Work/Personal/loopback4-example-socketio/tsconfig.json'
(Use `node --trace-warnings ...` to show where the warning was created)
(node:3894) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:3894) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
```
### Additional information
_No response_
### Reproduction
https://github.com/loopbackio/loopback-next/tree/master/examples/socketio
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in examples/socketio and reproduce the failure with `lb4 example` using the socketio option. Inspect the example's tsconfig.build.json and the CLI download/extraction entry point; done means the example can be downloaded and run end to end without the reported ENOENT or CORS failure, with REST and Socket.IO available together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100