mirror of
https://github.com/logos-messaging/docs.waku.org.git
synced 2026-01-05 22:33:06 +00:00
35 lines
2.4 KiB
Markdown
35 lines
2.4 KiB
Markdown
|
---
|
||
|
|
title: "Run @waku/sdk in a NodeJS Application"
|
||
|
|
---
|
||
|
|
|
||
|
|
While the `@waku/sdk` package is primarily designed for browser environments, you can use it in a NodeJS application. However, there are certain limitations and considerations to keep in mind. This guide provides a comprehensive overview of using `@waku/sdk` in NodeJS.
|
||
|
|
|
||
|
|
## Limitations
|
||
|
|
|
||
|
|
### API Compatibility
|
||
|
|
|
||
|
|
`@waku/sdk` prioritises browser compatibility, avoiding NodeJS APIs for simpler bundling. This design choice enhances browser API compatibility but sacrifices NodeJS optimisation. While many browser APIs work in NodeJS, they might need better optimisation.
|
||
|
|
|
||
|
|
### Protocol Implementation
|
||
|
|
|
||
|
|
`@waku/sdk` focuses on the client side of the [Request/Response protocol](/overview/concepts/network-domains#requestresponse-domain). We'll have to replicate all the functionalities added to [nwaku](/guides/run-nwaku-node) to implement extra features.
|
||
|
|
|
||
|
|
### Codebase Complexity
|
||
|
|
|
||
|
|
Balancing browser and NodeJS compatibility while maintaining simplicity adds complexity. A potential fix is making a NodeJS package that wraps `@waku/sdk` for smoother NodeJS development.
|
||
|
|
|
||
|
|
### Browser-Specific Logic
|
||
|
|
|
||
|
|
Certain features in `@waku/sdk` are tailored for browsers and might not translate seamlessly to NodeJS. For example, [Relay protocol](/overview/concepts/protocols#relay) in browsers requires unique [transport methods](/overview/concepts/transports) such as `WebTransport` or `WebRTC`, which might not align with NodeJS networking capabilities.
|
||
|
|
|
||
|
|
### Peer Management
|
||
|
|
|
||
|
|
`@waku/sdk` default peer management caters to the browser's ephemeral nature, which is different for NodeJS. This is why [DNS Discovery](/overview/concepts/dns-discovery) and [Peer Exchange](/overview/concepts/peer-exchange) are the default discovery mechanisms for the browser but not for NodeJS and desktop applications.
|
||
|
|
|
||
|
|
## Recommendations
|
||
|
|
|
||
|
|
Considering these limitations, consider your use case before opting for `@waku/sdk` in NodeJS. For a more optimised solution, we recommend [running nwaku in a Docker container](/guides/nwaku/run-docker) and consuming its [JSON RPC API](https://rfc.vac.dev/spec/16/).
|
||
|
|
|
||
|
|
## Future Developments
|
||
|
|
|
||
|
|
There are plans to release a NodeJS package based on [nwaku](/guides/run-nwaku-node) to streamline the process of using Waku Network features in NodeJS applications. You can track the progress and updates here: <https://github.com/waku-org/nwaku/issues/1332>.
|