max-mapper / max-mapper/websocket-stream
how to use in nativescript?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 667
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
var ws = null
if (typeof WebSocket !== 'undefined') {
ws = WebSocket
} else if (typeof MozWebSocket !== 'undefined') {
ws = MozWebSocket
} else {
ws = window.WebSocket || window.MozWebSocket
}
module.exports = ws
nativescript is some way like react native
and there is no window in it.
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
Review the WebSocket selection snippet in the issue and compare its window-dependent fallback with the NativeScript environment. No file or test is named, so first locate the package entry point and existing environment checks; the work is done when the intended NativeScript usage or compatibility change is verified without relying on window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100