-
Notifications
You must be signed in to change notification settings - Fork 2
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
2024-04-04 meeting #64
Comments
Mentioned in the Matrix room before, we are planning to schedule the standards session at the Node.js collaboration summit after the first 30 minutes of WinterCG meeting (16:00-17:00, London time) openjs-foundation/summit#398 Remote participation is open to everyone, we plan to use Zoom. |
Import Attributes have landed unflagged in NodeJS 18.20.0! import foo from './foo.js' with { type: '...' } The current landscape in browsers looks like something like this:
Would the group be interested in discussing the merits of this during the meeting? Unlike JSON, the rest of these formats will require some assumption about the DOM it seems like. So perhaps those could be optional for a runtime to support / shim (for SSR use cases)? |
If you want to hang out in the standard session of the Node.js collaboration summit (16:00-17:00, London time), check out openjs-foundation/summit#387 for remote attendance info.
|
Probably not enough time and so maybe I will take it to Matrix but had a little time to catch up on https://github.com/wintercg/proposal-functions-api and had a couple questions for the group on how to best continue advancing it along. (or any of my topics can be saved for next month too, that works for me 👍 ) |
To make time for Collab Summit, I'll push off the topic of Import Attributes until the next meeting, and thanks for all the feedback on getting started with the Function API proposal. 👍 |
wasmer
key for Wasmer Edge runtime-keys#10The text was updated successfully, but these errors were encountered: