Comments (17)
RE Modules WG meeting:
I'll take up lead for this use case meeting if needed.
from modules.
We might want to flesh it out within ourselves first, before sharing more widely - we'll certainly want a wider audience to ensure we're not missing anything, but the more complete a list we have before that, the easier it will be to minimize noise.
from modules.
@jdalton since we are not doing a meeting anymore would it make sense to open a fresh thread?
@bmeck should we close this?
from modules.
from modules.
I'd love to participate if my schedule allows for it
edit: I would like to see this happen before our next meeting if the timing can work
from modules.
Would it make sense to start of with collecting use cases first in the broadest sense possible and then drilling down? E.g. right now "specific existing libraries of specific importance" seems rather abstract. If it's "library X needs Y and has Z users", the decision would become easier (at least for me). Similar with other bullet points: Would there be use cases that are specific to nashorn? Would they sound reasonable to consider? Actually having 1-2 might make that an easier call.
I would suggest a brainstorm google doc and/or issue to understand the problem space before drawing borders.
from modules.
superceded by doc below
Well my concern is that we have a lot of things in Goals, but they aren't actions that actors (code authors, node program users, etc.) are able to do with a workflow of specific actionable tasks that they are trying to achieve and steps that are required to achieve them. I don't think stating the importance of a specific library would be beneficial, but some use cases are constrained to a very small subset of libraries like how JSDOM is the main library to look towards for a usage of "create an entirely isolated user land module system".So, the use cases document should be about task that can be performed and how in actionable ways / lists of actions. I've setup a google form that we can dump into and try to have before any call takes place at https://goo.gl/forms/4sGpG4OP2oxDG39U2 but am open to changing that form as seems desirable before the call. If something does not fit that form we should try and discuss scope of use cases that are not isolated and are affected by various existing ecosystem concerns.
from modules.
Linking @ceejbot's gist here as well for visibility: https://gist.github.com/ceejbot/d8703c71dd5cfba4ba93e755371e96e7
Do we want to spread the word about this beyond this group / actively seek community input? Or would this just lead to noise and bike shedding?
from modules.
Freestyle doc link here.
from modules.
Thanks for copying all the existing data! 🎉
from modules.
I'm fine closing this if some other issue is open w/ the doc link.
from modules.
Shall we get a PR going to bring in the items from https://gist.github.com/ceejbot/d8703c71dd5cfba4ba93e755371e96e7?
from modules.
Ah, forgot we were working to the Google doc at https://docs.google.com/document/d/10BBsIqdAXB9JR2KUzQGYbCiVugYBnxE4REBakX29yyo/edit.
Once approved and fleshed-out should we aim move those items into this repo though still?
from modules.
Once approved and fleshed-out should we aim move those items into this repo though still?
Sure, it's good to have these things documented and findable in some way (doc, wiki, link).
from modules.
I added a few more web-oriented use cases. Is the Google doc the canonical location for now?
from modules.
Is the Google doc the canonical location for now?
Yep :)
from modules.
Closing in favor of #55
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.