Skip to content

Commit

Permalink
doc: added meeting notes 2023-06-26 (#100)
Browse files Browse the repository at this point in the history
Co-authored-by: Vinícius Lourenço <vinyygamerlol@gmail.com>
  • Loading branch information
2 people authored and rluvaton committed Apr 8, 2024
1 parent 604af76 commit 214fbd1
Showing 1 changed file with 48 additions and 0 deletions.
48 changes: 48 additions & 0 deletions meetings/2023-06-26.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
# Node.js Performance Team Meeting 2023-06-26

## Links

* **Recording**: https://www.youtube.com/watch?v=UQzj2Ezu1jU
* **GitHub Issue**: https://github.com/nodejs/performance/issues/97

## Present

* Performance team: @nodejs/performance
* Ulises Gascon: @ulisesGascon
* Vinícius Lourenço: @H4ad
* Carlos Espa: @Ceres6


## Agenda

## Announcements

No announcements

### nodejs/performance

* Performance of WHATWG ReadableStream.read() [#82](https://github.com/nodejs/performance/issues/82)
* No news
* Expensive `isTraceHTTPEnable` [#81](https://github.com/nodejs/performance/issues/81)
* Vinícius made a good progress (compilation issue solved)
* Waiting for review. See: https://github.com/nodejs/node/pull/48142
* @anonrig can help us to speed up the review
* Improve legacy CJS resolve [#73](https://github.com/nodejs/performance/issues/73)
* Vinícius added new tests
* Vinícius detected a bug on his own code but he is in the way to fix it, which was related with the resolution on windows.
* MakeCallback is very slow [#24](https://github.com/nodejs/performance/issues/24)
* No news
* Open for help from the community


## Q&A, Other

* Fast path for --no-deprecation [#90](https://github.com/nodejs/performance/issues/90)
* This is a good first issue for the community
* Carlos will lead it

## Upcoming Meetings
* **Node.js Foundation Calendar**: https://nodejs.org/calendar

Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

0 comments on commit 214fbd1

Please sign in to comment.