Websocket connection or importing packages
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, vite
- Domain
- mobile
Research direction
Start by determining whether the background runner supports WebSocket connections and package imports with Vite, Ionic 6, and Vue. Establish a reproducible example and define the expected background behavior; done means a documented or implemented supported path.
Written by the indexing model from the issue text.
Description
Hi, I created my own background runner and it is working ok, with basic JavaScript. The problem starts when i need to connect using Websocket. I also tried to import some packages but i wont let me do it. Is there any option to bypass this problem, or some how run Websocket connection in background? Im running vite, Ionic 6, vue.
- Dominant language
- C
- Stars
- 57
- Forks
- 37
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Getting set up
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.
More from ionic-team/capacitor-background-runner
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
ionic-team/capacitor-background-runner#158 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ionic-team/capacitor-background-runner#155 · 1 reaction ·
-
Capacitor keeps running old background runnersMay be free again @theproducer claimed this 244 days ago, and no pull request is open. Openbug
ionic-team/capacitor-background-runner#152 · 1 comment · 2 reactions · 1 assignee ·
All issues in ionic-team/capacitor-background-runner
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
trezor/trezor-firmware#7997 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area/ysql kind/bug priority/medium status/awaiting-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yugabyte/yugabyte-db#34415 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
KhronosGroup/OpenCL-Headers#318 ·
-
0.kind: build failure
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day