Modern development environtment using a vite monorepo with materialize as a package

[danice]

I have done a proof of concept project that re-creates the materialize website as a vite project, including materialize current project as a monorepo package (and as a git submodule).
Main advantatges are:

• you see immediately the result of any changes in the components or website files. Nothing is needed to see the change, just wait 2 seconds for vite to apply the changes to the browser.
• the environment warns immediately of any typescript incorrection
• you don't need any pug processing, using some kind of vite includes (see README file)
• you don't need webpack to publish the result, "vite publish" now can perfectly replace webpack
• its a good development env model for any team that needs to add or fix functionality to materialize without having wait the changes are included or having to generate its own package

Of course with such a big change I not pretend the website is working 100%, it has obvious missing parts, but this only affects to the website, the components itself are completely functional.

Here is the project, try it and tell me what do you think or if you find any problem...

[wuda-io]

Hey @danice!
I would like to seperate the website from the materialize-core project just like you did.
It is a great idea and i think we can move a lot faster from there.
I will test your proof in the upcoming days and give feedback here. If it is working mostly it would be cool if we can implement it here.
Is this ok for you? Thanks for your effort in bringing Materialize some steps further.

[danice]

Of course that project's code or some modification could be used as a base for a new website project.

After a little more thoughts and working more with materialize project "dev" script, I have to update the previous list of main advantages.
The current project "dev" script also reflects changes in components pretty fast... the main advantage of this proposal is that the "monorepo" project is typescript project using materialize as a package similar as it would normally used (but a locally generated copy, see Pnpm Workspace protocol).
Also it seems that vite is much better and future-proof that webpack as it uses native ES Modules without need of the bundle step (except for production generation).
Also, for advanced projects that need to do changes in the components without waiting for that changes to be included in the official repository, a monorepo structure like this is very convenient, and sometimes could be preferred to use the library that way instead of just like a regular packages.

Finally, using pnpm instead of npm (that now also allows workspaces) is simple because it dramatically saves disc space and is much faster.

Please tell me if you find any problem or any thoughts... of course the new project development environment should be open to a discussion of benefits / inconvenients from all collaborators.