David Burles

Absolutely. By the way, thanks for creating this useful utility. Rather than providing a single entry-point, instead the package is consumed via deep imports. It's an ideal approach for publishing...

Sorry, the `"."` export field.

Hey @marvinhagemeister any movement on this one? Would love to be able to make use of this utility in my packages. I'd be fine with a cli option.

Hmm, say the Documents collection example is updated to include firstName and lastName fields you could then write something like this as an example: ``` js Documents.helpers({ fullName() { return...

> 1. There is an exports field in the package.json https://unpkg.com/browse/@n1ru4l/[email protected]/package.json Can you clarify what you mean? > 2. I dont like that as it does not allow renaming and...

> If you want to reduce memory usage you can still bundle your server code and drop unused code via tree shaking. I don't see why deep imports (which limit...

Hey @n1ru4l, this repo gives a pretty good example where the problem can arise https://github.com/GeoffreyBooth/dual-package-hazard

> @dburles Can you provide an example woth packages in this mono-repo? That is not always easy to determine ahead of time, which is why it's a hazard that's best...

For some additional clarity, these packages are currently published correctly if they included only the `module` field. However, since they've been updated to export ESM with [conditional exports](https://nodejs.org/api/packages.html#conditional-exports) they are...

Here's a simple app (https://github.com/dburles/dph-graphql-live-query) that demonstrates how it's possible to import into memory and run two copies of the same function. The demo app is denoted as a "module"...