Kyle Davis

@rwwagner90 yeah I know it’s not supported, just meant that my previous update to the documentation around stopping the propagation of the events no longer works. So maybe we just...

The above errors appear to be from [yarn caching / not removing previous node_modules](https://github.com/moment/moment/issues/5024). [email protected] introduced a locale en-SG.js. Not sure what to do here...

Just wanted to check in here and see if there had been any further progress related to this issue. Thanks!

I was receving the same in a node environment (mono repo using all ESM packages) where i was importing from the tree-shakeable path: ``` import isEmail from 'validator/es/lib/isEmail'; ``` Importing...

There is also a similar issue when using composite fields that require coalescing in the index. If I try to create an index like so: ``` { indexes: [ {...

@Husamui try also setting an env variable DOTENV_CONFIG_PATH=path/to/.env.vault then update your dotenv.config to use that path in its options

@Husamui nevermind -- that was bad advice -- trying to sort through the same issue myself

@maxfierke That certainly fixed it -- and confirmed my stupidity, I appreciate it!

I think it is a bug with encapsulated tasks. Computeds do work on glimmer components although aren't always necessary. There's definitely still some issues with the non-ember objects with encapsulated...