Ben Ayala

May be related to #632

Same issue for me when using `import format from 'date-fns-tz/esm/format'` Looks like some `date-fns-tz` esmodules are importing *non-esmodules* in some instances. 

@emilast Hi friend, just wondering if the work on this extension is still ongoing? This would be a nice bug to fix, if possible. Thanks for your efforts!

I appreciate it, hope you have a great day

An alternative to keep the store in sync based on an component signal is to use an rxMethod ``` typescript export interface MyState { prop1: Prop1 | null; prop2: Prop2...

As a temporary workaround you can set the following in your settings.json ```json "workbench.colorCustomizations": { "editor.wordHighlightBackground": "#ffffff00", "minimap.selectionOccurrenceHighlight": "#ffffff00" } ```

```typescript //Custom Code openDeleteNeighborModal( neighbor: NeighborOut, body: TemplateRef ): void { const dialogConfig = getDefaultConfirmationDialogConfig({ width: '600px', title: 'Delete User', body, hasActionButton: true, actionButtonText: 'delete User', actionButtonSeverity: 'danger', dismissButtonText: 'Dismiss',...

I noticed #1603 has already been merged, so I checked the newest version of the extension in VSCode but still the issue is present. `Version 0.20251124.1`

~~I think this could be closed now! I just updated to version `0.20251127.1` and the error is no longer there. Thank u~~

@jakebailey oh you are absolutely right, I updated the extensions but didn't realize it was disabled. sorry about the confusion.