-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Updating polyscript to its latest #2128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
30d99b2
to
4a08e77
Compare
@mchilvers FYI all issues around SAB and named workers are automatically resolved by this latest version. I have decided to use a |
54c89a6
to
fc1750f
Compare
e8f77d2
to
28bc219
Compare
for more information, see https://pre-commit.ci
28bc219
to
b5a1161
Compare
e4e1c82
to
f2dd278
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A quick question about a hardcoded mpy
..! But otherwise LGTM. 👍
fba54f5
to
5133022
Compare
for more information, see https://pre-commit.ci
838bb1a
to
1ade26c
Compare
for more information, see https://pre-commit.ci
This is currently published as
0.5.0-rc4
on npm:https://cdn.jsdelivr.net/npm/@pyscript/core@next/dist/core.js
https://cdn.jsdelivr.net/npm/@pyscript/core@next/dist/core.css
Documentation
pyscript/docs#134
Summary
The latest coincident is being tested to provide the following features:
serviceWorker
orservice_worker
url is passed as options / config, it eventually does fallback to sync XHR based exchanges that makes it still possible to usewindow
ordocument
from workers, even if headers required to enabled native SharedArrayBuffer are nowhere in the project, thanks to sabayon helperThe current
polyscript@next
also has been improved to both use latest coincident and simplify the bootstrap logic, providing better ways to also understand whenwindow
ordocument
cannot be used, printing better / more meaningful errors too.The concept here is that as long as you don't try to use
window
ordocument
, you don't need to care about SharedArrayBuffer so that general DX should hopefully be better now.Literally nothing that was working before should break now, quite the opposite, it should be eventually slightly faster with more fine-tuned memory leaks prevention thanks to underlying libraries updates and the communication channel between multiple workers have been improved too.