Travis Tidwell

I actually agree with this change, but us using "cjs" for "import" was changed deliberately. Using mjs was causing some downstream issues with our build process and was not working...

Hello @manuelroth we will escalate this internally to see if we can reach some form of resolution.... thanks.

Angular 18 is currently supported within the RC releases of @formio/angular w/ the 5.x renderer. It should be noted however that you should not use "formiojs" with "@formio/js" since "@formio/js"...

We may need to make a change to our core library to use relative paths for the packages instead of those defined by "exports" within the package.json. My guess is...

Thanks for the bug report. We will reproduce on our end and add this to our developer backlog to get resolved.

1. This item has not been deemed as critical, so it may be at least 3-6 months before resolution. There is a way to expedite if you want to go...

This may have been fixed with my pull request @ https://github.com/formio/formio.js/pull/6054 and in particular the change made here https://github.com/formio/formio.js/pull/6054/files#diff-05d41a5d854049f92f62772ee82f295d614534d5f4f0717b3ec30c69dfc3a7f5R2905. Before it would set the default value to empty string instead...

I will take a look as soon as possible.

I don't think we should be automatically updating the symver automatically. I am fine with DEV tags, but there may be some bad side effects of this releasing the RC...

If you need to dynamically add new columns, then it may be easier to have the components already there, but conditionally hidden. Then, you can just add the data that...