lightninglabs / lightninglabs/lnc-web
The connection time is too long
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I am currently facing a problem in my frontend project to obtain https://lightning.engineering/lnc-v0.3.3-alpha.wasm The file is very slow, which leads to a long connection time and sometimes connection failure when calling the connect() method. This may be because I am in Taiwan, China, China. Can I put the file on our own server or in the front-end project? If this is possible, how can I do it? Or may I ask if there are any other methods?
// Create a new LNC instance
const lnc = new LNC({
namespace: id,
serverHost: serverHost,
wasmClientCode: 'Project local file routing or our server file routing'
});
Contributor guide
No contributing guide indexed for this repository
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 by tracing the LNC constructor and connect() call shown in the issue, then inspect how https://lightning.engineering/lnc-v0.3.3-alpha.wasm is obtained. Determine whether wasmClientCode can accept a project-local or self-hosted file and identify the relevant documentation or entry point. Done means a frontend can load the client from its own server or project without the reported connection delay or failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, wasm
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100