- 1 Agenda
- 2 Awesomeness Schedule
- 3 Bugs
- 4 Attendees
- 5 Minutes
- 5.1 High Priority Work
- 5.2 Blockers?
- 5.3 Roundtable
- High Priority Work
- Node Loader JEP
- Using OS.File? We have `io/fs`, `io/file`...
- Node APIs: `require('node/fs')`, living in `./lib/node`, or perhaps if there is a more common/generic name for node APIs, rather than the proper noun 'node'. 'commonjs' wouldn't work as that's what we are in m-c. But this is a good, clear distinction between Firefox-y 'sdk' and general JS utilities 'node' (but again, a generic name)
|Awesome Date||Awesome Person - Awesome thing|
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
High Priority Work
Matteo sick last week, not much update. Erik's waiting on reviews for the toolbar stuff.
Eddy: went through bugs. emailed Mike.
Erik: nothing new, just working on it.
Blocked on getting uplift into tree, should happen today.
[Slaughterhouse] (needs public bug)
Gabor: meeting booked, we'll discuss there. Otherwise not much update.
Jordan: waiting for uplift to fix it.
Jordan: making progress on this.
Support for node dependencies. With this we could use npm for Jetpack modules. Irakli: how does this mesh with Erik's work? Jordan and Erik need to figure this out.
Using OS.File? We have `io/fs`, `io/file`...
Mossop: OS.file is totally asynch. Irakli: we should use OS.file in io/fs.
Node APIs: `require('node/fs')`
Jordan: we should have a namespace for SDK modules that are essentially clones of node modules in the SDK require tree? What should it be called? Mossop: "node" is fine. Move node-clone modules there (path and io for instance).