I'm excited to move away from window.OC to the @ nextcloud packages in most cases and I recently added @nextcloud/auth to one of my Nextcloud apps. 🤓 This package, in turn, requires @nextcloud/nextcloud-bus, which unfortunately, seems to have had a considerable effect on bundle size. Right now, it's 13.41 % of the whole app's bundle.

/node_modules/@nextcloud/event-bus/dist/index.es.js
██████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 13.41 % (113.459 KB)

I quickly looked through this repository and I can't see any apparent reason why the code transpiles to more than 100 KB, maybe it is the import of semver? Or maybe it is simply legacy browser-support? Any ideas on how to reduce the size? 😊

Currently semver breaks IE11.
So we need to manually add it to the transpile set of babel

Since we're transpiling here too, either we don't at all or we should transpile the dependencies that are problematic 🤔

~/Docker/apps2/viewer% npm ls semver
viewer@1.4.0 /home/admin/Docker/apps2/viewer
├─┬ @nextcloud/auth@1.3.0
│ └─┬ @nextcloud/event-bus@1.2.0
│   └── semver@7.3.2 

Thoughts?
cc @nickvergessen @ChristophWurst @juliushaertl @georgehrke

Hello, please update the package on npmjs because it says unsupported engine when installing with npm.

Memories currently uses an extension of the event bus to get static typing on event names and callbacks; see:

https://github.com/pulsejet/memories/blob/f5627da48868988615f17e5a5b66215cabf37323/src/services/utils/event-bus.ts#L5

Would you be interested in such an implementation to be merged upstream?

@skjnldsv @susnux

Intro

Welcome!

Since I find it quite awesome that we can use global events, I think we should aim for a nice convention.
Let's list an example of potential events we could see across Nextcloud... 🤔

Thoughts

• A file have been updated
• An app have been enabled/disabled
• A contact have been deleted
• A file have been uploaded
• A header menu have been opened
• The sidebar have been toggled
• ...

Goals

I think it would be nice to have some kind of modifier syntax.
I really dislike underscores, so I would favour dashes.

Proposal

• files:file.update
• contacts:contact.delete
• nextcloud:app.disable
• nextcloud:unified-search.search

Sub-proposal

I would love to be able to watch for partial event names.
Like file:update:12345 and file:update would both trigger if the file 13245 is updated?

Questions

• Shall we enforce the dashes and throw errors
• Shall we strongly suggest the syntax event:modifier:data (e.g. file:update:12345)
  • If so, the header-menu-unified-search:open should most likely be header-menu:open:unified-search ?

Thanks!
cc @georgehrke @korelstar @ma12-co @juliushaertl @ChristophWurst @raimund-schluessler @danxuliu @rullzer

There should be a dist/index.d.ts but it's in dist/lib/index.d.ts for some reason.

Module work anyway, but IDE support is subpart.