-
I have a simple `Procfile` that looks like this:
```
web: bin/rails server -p 3000
worker: bundle exec sidekiq -t 25
```
When I do `overmind start -f Procfile` it throws this error:
```
$…
-
Web Workers resolve to the `browser.js` however `window` is not defined thus causing an undefined reference.
Using `globalThis` or `self` instead of `window` could allow this file to work in web work…
-
![Quicker_20240515_180110](https://github.com/C3ting/ARL/assets/46021651/447f94b1-d2d5-4245-9155-97452e160deb)
-
### Describe the bug
Please refer to this repository for a way to reproduce the issue: https://github.com/gabrielecirulli/vite-pixi-bundling
When bundling Web Worker code with Vite, some of the de…
-
**Description**
[Web Workers API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers) instead of sources of a file gets source of the `index.html`.
I mean `fetch()`…
-
### Description
Web workers are broken on legacy mode, althought caiuseit shows it can be used on legacy browsers(IE10+ supports for example non-shared web workers). Not even a warning is displayed t…
-
### What is the problem this feature will solve?
Creating cross-platform (Node.js + browsers) code has never been more important, but there are still some sharp edges. `fetch` support was recently …
-
-
### Feature Description
When dealing with huge entities with lots of one to many and many to many joins, the typeorm hydration process takes a painful amount of time. This has been highlighted in …
-
### Describe the problem
I wasn't sure whether to list this as a bug or not, but I'm not able to use `fetch` from `@tauri-apps/api/http` in web workers.
Considering that the browser native fetch [su…