Brett Willis

I see, so it depends on the style of import where the module is imported, not so much the module itself. [Here is a full representation of my scenario](https://esbuild.github.io/try/#YgAwLjIxLjMALS1idW5kbGUgLS1mb3JtYXQ9ZXNtAGUAZW50cnkuY2pzAGNvbnN0IGlzRXF1YWwgPSByZXF1aXJlKCcuL3dyYXBwZXIuY2pzJykKY29uc29sZS5sb2coaXNFcXVhbCkAAGlzLWVxdWFsLm1qcwBleHBvcnQgZnVuY3Rpb24gaXNFcXVhbChhLCBiKSB7fQAAd3JhcHBlci5jdHMAaW1wb3J0IHsgaXNFcXVhbCB9IGZyb20gJy4vaXMtZXF1YWwubWpzJwpleHBvcnQgPSBpc0VxdWFsOw), btw....

Ok while there is opportunity to optimise the output I understand your explanation, thanks!

Sure, note these are private org dependencies, but hopefully the info can tell you what you need. ### Step 1 `package.json` ```json { "dependencies": { "@arrowheadapps/billing-engine-core": "1.0.89", "@arrowheadapps/billing-engine-platform-core": "1.0.89" }...

Hi @lehcar09 thanks for your effort investigating this! Given your indication that app resources do not affect the source mapping, perhaps that may hold the solution. Currently there's a circular...

I suppose another option: add a `merge: false` or similar option to `update()` to disable top-level merging. However `update()` also has the key-value-pair arguments option so would make it less...

@cherylEnkidu thanks for your reply! Yes an atomic read-write (`get()` and then `set()` within a transaction) can also effectively enforce an existence "precondition" there a couple of fundamental differences: -...

@cherylEnkidu another use-case: Say one wants to do a deep merge, using atomic `FieldValue` operations (without reading and holding a lock on the document) and to ensure that the document...

Thanks @cherylEnkidu is this a case where community contribution would be accepted, or does it need to go through the core team due to API design?

Understood, thanks.

I've run into this one, too: `TODOError: Re-enable ReadableStream support in spawn stdin.`