Comments (23)
I'd like to push us to avoid discussing general technical PRs in the meeting this week.
A rough agenda that I can update above if people are onboard (if yes please use emoji repsonse, if no please explain why)
- Quick review of outstanding PRs against this repo
- Reach consensus on how we should handle current PRs against core
- Discuss use cases and try and put together a base list that we reach consensus on in the meeting to avoid another 2 weeks before we can land anything
Thoughts?
from modules.
from modules.
@jdalton or @devsnek would either of you be willing to present the console.log
extra stack frame issue in the meeting so we can solicit more eyes on it and land?
I'm opening another issue to discuss in the meantime
from modules.
I can talk about it I guess, it was a concern originally brought up by @TimothyGu
from modules.
Apologies I'm unable to attend and, ultimately, unable to contribute much too ... thanks gosh I agree with whatever @jdalton says so I feel well represented 😅
If I cannot fix my useless presence in here I'd be happy to be moved to observer state ... just please give me some more time to figure out if I have those 5 hours of duty per week I've said I would.
Regards
from modules.
Should we identify a single focus topic / deep dive for this meeting? E.g. getting a good, exhaustive list of use cases we can agree on? Or are we punting on that until April 3rd (or whenever the module summit will be)? It felt like the last meeting got dragged down by the back-and-forth between "answer minor question X" and "we need a general agreement on what we're trying to build here".
from modules.
I'm traveling and I probably won't be able to join. I'm ok with whatever decision the team is going to make. Feel free to not count me towards quorum.
The agenda seems too big for one single meeting, should we prioritize a bit?
from modules.
I will also be traveling and unable to make the call this week.
from modules.
from modules.
Maybe weird request?
I'd prefer it if we started with technical discussion of the nodejs/node technical issues and I ask that people who would like to participate in that discussion enter the actual issues (I try to ping @nodejs/modules on issues when I see them).
Namely,
- I'd love to hear an update about wasm from @linclark in "loader: allow importing wasm modules"
- I'd love us to vote about the
_
issue in "esm: provide named exports for all builtin libraries"
from modules.
By "the underscore issue" do you mean filtering _
prefixed members from the exposed exports?
from modules.
We can remove the mode: "esm" flag item from the agenda, as we already discussed this briefly last week.
from modules.
@weswigham yes
@guybedford how do we proceed with the esm flag item? Don't we need to make a decision about it?
from modules.
@benjamingr I'm ok with putting this on the back-burner while we focus on other technical decisions and use cases.
from modules.
I'd love us to vote about the _ issue in "esm: provide named exports for all builtin libraries"
The PR isn't blocked on filtering of _
at the moment. That was worked through a bit ago.
from modules.
@jdalton thanks for the update, reading it: I don't really understand why it's stalled. How can core move forward with named exports for ESM? What needs to be decided before the PR lands?
from modules.
I don't really understand why it's stalled.
It's stuck on a console.log
stack count nit at the moment.
What needs to be decided before the PR lands?
Minor things are left, for example now that live bindings of named exports works should setters still be filtered. That said, with the push to remove getter/setters from builtin module exports started before live bindings were thought possible and with things still being experimental, it may not be a super concern esp. for initial support.
from modules.
@jdalton thanks, is this something you think we need to discuss in the meeting, spin off into an issue here or discuss in the main nodejs/node repo? I really want to see named exports for native modules land :)
from modules.
thanks, is this something you think we need to discuss in the meeting, spin off into an issue here or discuss in the main nodejs/node repo?
I think it just needs someone to pop-in and fix the console.log
stack issue or better yet find the root cause of the console.log
reference issue and fix that.
I really want to see named exports land :)
Same.
from modules.
@MylesBorins sorry I can't make it to today's meeting. Will catch up tomorrow.
from modules.
I'll only be able to join but need to drop off after the first 30min.
from modules.
Hey All, I've updated the agenda based on #47 (comment) which significantly simplifies the agenda and puts it into subcategories and time boxes for each discussion.
from modules.
Here is the link to join y'all https://zoom.us/j/656987750
from modules.
Related Issues (20)
- Mocking use cases HOT 13
- Enabling import meta resolve by default? HOT 16
- Relaxing the '#' restriction on imports HOT 8
- Node.js Modules Team Meeting 2020-09-09
- Node.js Modules Team Meeting 2020-09-23 HOT 1
- Document node: scheme HOT 4
- Clarification for bundlers re "import" / "require" matching HOT 7
- Node.js Modules Team Meeting 2020-10-07 HOT 3
- File URL normalization changes HOT 1
- s/master/main HOT 3
- Node.js Modules Team Meeting 2020-10-21 HOT 4
- Experimental Status HOT 18
- Node.js Modules Team Meeting 2020-11-04
- Archiving modules repo and stopping team meetings HOT 1
- Use existing context for SourceTextModule evaluation? HOT 2
- Node.js Modules Team Meeting 2020-11-18
- import local files fails while import() succeeds HOT 5
- Proposal: ESM should not export PromiseLike instance HOT 5
- `import.meta.url` is `undefined` inside module file. HOT 3
- Extensionless files should allow --input-type (or work) HOT 14
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from modules.