Closed SMotaal closed 6 years ago
Hey @smotaal, would be more than happy to add you as an observer once we have a chance to finalize our governance around it. In the mean time we can add you as an invited observer to the next meeting.
FWIW if the major thing you are interested in learning about are Native Modules this may not be the best space for you to do research as we are hyper focused on ESModules currently, and have not dug too much into the native-module space. You might be interested in getting involved with the node-addon-api
team which can be found at https://github.com/nodejs/node-addon-api. There are weekly calls and a bunch of work being invested into improving the native module sotry
@mhdawson should be able to chime in if I am directing you to the incorrect place, but opening an issue on the above repo should get the right people there to point you in the right direction.
@MylesBorins poor choice of words, intended true ES modules sic (natively implemented by the platform)
Thanks! I’m looking forward to appreciating all the hard work you guys are putting in to this long and equally worthy topic.
welcome to the team
@MylesBorins, I just realized I never got back to this. So do I need to PR or did we change the process.
Everything is done. No need to open a pr
On Fri, Jun 8, 2018, 3:10 PM Saleh Abdel Motaal notifications@github.com wrote:
@MylesBorins https://github.com/MylesBorins, I just realized I never got back to this. So do I need to PR or did we change the process.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nodejs/modules/issues/68#issuecomment-395755790, or mute the thread https://github.com/notifications/unsubscribe-auth/AAecV8z4hm8tzpP2-5YFf8IT2gnh4X3Uks5t6nengaJpZM4TW2A4 .
I'm currently developing an open source JS as 4GL environment (for on going research and public use of various image analysis and conformance testing for multiple ISO printing quality standards).
Unfortunately, I spend most of my time trying to figure out how to make use of ES modules across NodeJS and Electron (even NW for a period) as modules are the most critical deciding factor for the design of the environment.
The goal is to not subscribe to legacy/bloated workflows (ie simulating ES modules) so that it can efficiently handle change to modules. This is currently accomplished using an experimental fast translation layer that can independently compile other languages (just TypeScript at the moment) without the additional and seemingly unavoidable overhead catering to build-time oriented workflows, which is normally embedded in the foundations of such libraries.
It would be extremely helpful if I am able to observe instead of the many hours wasted trying to figure out from sparse threads scattered across multiple projects the direction and rationale behind the committee's efforts. I am only interested in observing, willing to assist only if asked to do so.
Thanks