This repository was archived by the owner on Jan 10, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 10, 2020. It is now read-only.
Plan public Node.js User Feedback session for 2018-03-30 #38
Description
dshaw
Issue body actions
- Attendees:
- @nodejs/user-feedback
- @boneskull - Mocha
- @TheLarkInn - webpack
- @iarna - npm
- @jchip - Electrode, End User representative
- @nodejs/modules
- Topics:
- Describe how your Tooling leverages Node.js.
- Why do you use Node.js for Tooling?
- What's working in the Node.js tooling ecosystem?
- What isn't working in the Node.js tooling ecosystem?
- What's new that could impact Node.js?
- Desired outcomes:
- Greater insight into the needs of Tooling authors needs
Reactions are currently unavailable
Activity
Topics:
- What's working in the Node.js tooling ecosystem?
- What isn't working in the Node.js tooling ecosystem?
Topics (for feedback):
- Tracking Issue for Runtime Deprecation of Buffer constructor -
Tracking Issue for Runtime Deprecation of Buffer constructor node#19079
- Tracking Issue for Runtime Deprecation of Buffer constructor -
Topic:
- Using N-API
Topic:
- Is there anything the Node.js Project and/or the Node.js Foundation could do to better support your needs?
Invite @kborchers and JS Foundation representatives.
the sean larkin you want is @TheLarkInn
The first and only Sean Larkin. Thanks, @boneskull.
I can attend on behalf of the @ember-cli team.
Reacted by Christopher HillerDan, I'll attend for team Intel. Is there timing information somewhere?
Closing, since this is a past meeting. Thanks for attending everyone! We look forward to continuing to work with y'all more in the future.