Henry Ing-Simmons

I'm getting the same issue in a normal component (which is called from a StatelessComponent) ``` Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a...

Any updates on this?

Is this still not done? 🤣 I abadoned atom for VS code 10 months ago because of this

The notice here is really unclear: `Notice: dayjs.tz.setDefault will not affect existing dayjs objects.` This sounds to me like: ```ts const value1 = dayjs("2021-05-18T14:44:00.000Z"); dayjs.tz.setDefault("Etc/UCT"); const value2 = dayjs("2021-05-18T14:44:00.000Z"); //...

Anyone maintaining this repo?

This makes sense and I can understand why a lot of people wouldn't want this as standard. I can appreciate if its not top priority on your roadmap but thanks...

These issues should also be closed if the build is reran and suceeds

This makes sense so I can see why you wouldn't want to delete the branches for failed builds. No this isn't working for me you can see in my screenshot...

I've been going through the versions and it looks like `v0.4.10` is when it started breaking. Which looks like when you introduced the dependency on `@vue/runtime-core` and `@vue/runtime-dom`: https://github.com/victorgarciaesgi/vue-chart-3/compare/v0.4.8...v0.4.10 >...

I'm getting a new error now: ``` Property 'class' does not exist on type 'Readonly'. 25 | return ( 26 | 27 | class="position-relative h-100" | ^^^^^ 28 | chartData={chartData}...