How do you intend files to be served?

[Steven-Nagie]

Is your intention that index.html is viewed as file:/// in the browser? If so, there are CORS issues with the javascript files treated as modules.

Or is the intention to serve some of the files via express or similar?

Or is there a run command in boreDOM that I don't see?

Either way, can you update the README? It's a fun experiment, but I can't figure out how the framework is intended to be used.

[HugoDaniel]

Hi @Steven-Nagie, I'm sorry I did not see this issue before (it has now been... 6 months? 😵). The initial idea for this was to be served using some sort of local HTTP server. I have been using python3 -m http.server on the command line, but I think any HTTP server might do the trick, like standard ones such as apache/httpd or nginx.

Again I'm sorry i could not anwser before, I really was not expecting anyone to engage with this and have been away from Github.

Let me try to put together a simple way to start this project and follow your suggestion to update the README for a more welcoming one!

[HugoDaniel]

Just updated boredom to include a cli tool (called "boredom") to serve local files, automatically update the index.html with the components as they are updated/created/removed, and do the static build in a build folder.

Wrapped it in a convenient startup script, if you run pnpm create boredom@latest my-project it will create a template project and configured boredom cli tool for it, ready to start creating something with boredom.

If you want to deploy the project somewhere the whole final thing is sitting in the build/ folder as static project, useful for github pages or any other static files service.