I think this is a good idea, but if I can make a suggestion: it would be very nice if building the web.js also output it into the ui/public folder. This way it can also be hosted by Flowise itself, instead of relying on a CDN. This has the added advantage of any changes being done in the embed bot will be immediately reflected.

The embed sample can also be updated to use the local version instead of CDN, or both.

Also this would eliminate the dist folder from the embed repo which would be good, it probably shouldn't be there to begin with.

@automaton82 Great suggestion. I'll add that as well. I'm also including a demo project for testing the embeds. This should help us iterate on changes in embeds quickly.

But I'll keep the dist folder for now, just in case someone wants to download the build output from Github. Later I want to have downloadable files under Releases at which point we can remove the dist folder completely.

@0xi4o let me know if this is ready for review, and the errors on the CI/CD are fixed (linting issues)

@0xi4o let me know if this is ready for review, and the errors on the CI/CD are fixed (linting issues)

putting on hold until #1272 is merged

👍
#1272 is merged, hope to see this merged too :) Do you guys need any help with this one?