- Darcy Clarke (@darcyclarke)
- Matt Hayes (@mysterycommand)
- Owen Buckley (@thescientist13)
- Luke Karrys (@lukekarrys)
- Zbyszek Tenerowicz (@naugtur)
- Housekeeping
- Introduction(s)
- Code of Conduct Acknowledgement
- Outline Intentions & Desired Outcomes
- Announcements
- overrides shipped
- Issue: #497 [RRFC] Warn users when skipping alias/git deps during audit - @rotem-cider
- Issue: #999 [RRFC] Custom logging location - @EvanCarroll
- Dsicussion: #496 Mention workspace in run-script output header - @smhg
- PR: #488 Make npm install scripts opt-in - @tolmasky
- PR: #481 RFC: Run `prepare` Scripts for Linked Bundled Dependencies - @mysterycommand
- PR: #375 Define which dependencies are shared among workspace projects - @isaacs
Issue: #497 [RRFC] Warn users when skipping alias/git deps during audit - @rotem-cider
- @darcyclarke
- we're planning to revamp
npm audit
&npm install
output to make this issue less relevant - explicitely defining which deps get audited & whu will help mitigate confusion
- we're planning to revamp
Issue: #999 [RRFC] Custom logging location - @EvanCarroll
- @lukekarrys
- currently
npm
owns the cach directory - we're looking to separate the logs from the cache/log directory
- we will only let you determine the directory path & not the file name
- 👍 to this - is a net-new flag
- currently
- @fritzy
- we should maybe name this appropriately like,
--unmanagedLogDir
or something similar
- we should maybe name this appropriately like,
Discussion: #496 Mention workspace in run-script output header - @smhg
-
...
-
@darcyclarke
- 👍 for this
- aligns with the work we'd like to do
-
@lukekarrys
- likes this
- would have treated this like a bug fix if it didn't come through discussions
- prefixing is very interesting/compelling as well
-
@naugtur
- can
publish --dry-run
support this aswell?
- can
-
@darcyclarke
- yes, let's have any workspace-aware command support logging the context
PR: #481 RFC: Run `prepare` Scripts for Linked Bundled Dependencies - @mysterycommand
- @mysterycommand
- no update
- was able to get a hacky work around for this
- only works one level deep
- @darcyclarke
- sounds like
yarn
doesn't support this either
- sounds like
- Actions:
- @mysterycommand to investigate how yarn handles this
- @darcyclarke to investigate https://turborepo.org/docs/features/pipelines
PR: #488 Make npm install scripts opt-in - @tolmasky
- @naugtur
- has done some investigation here
- worked with maintainer of lavamoat
- ...