New build

[jfhenon]

PR description

This PR has the goal to simplify the build process using the latest rollup/babel updates offering modern browsers light solution but also keeping support for older browsers.
We may also include in this PR some npm packages that are now imbedded in the project and not updated (which ultimately can cause bugs and security issues).

NOT READY TO MERGE BUT FOR INITIAL COMMENTS/CONTRIBUTIONS

Checklist

Note that we require UI tests to ensure that the added feature will not be
nixed by some future fix and that there is at least some test-as-documentation
to indicate how the fix or enhancement is expected to behave.

• - Added Cypress UI tests
• - Ran npm test, ensuring linting passes and that Cypress UI tests keep
  coverage to at least the same percent (reflected in the coverage badge
  that should be updated after the tests run)
• - Added any user documentation. Though not required, this can be a big
  help both for future users and for the PR reviewer.

[jfhenon]

should add to the documentation:

• svgedit.html is now index.html (es version) so you can just type: http://localhost:8000/dist/editor
• other versions can be accessed with a different html: http://localhost:8000/dist/editor/index-iife.html or http://localhost:8000/dist/editor/index-umd.html
• The source file can also be tested using http://localhost:8000/src/editor
• build is just npm run build (the rollup config will do the rest)

[jfhenon]

Now, css and modules are added using standard css3/es6 syntax. It works well with esm but not tested on old browser.

[brettz9]

I haven't dived too deeply into the details of the Rollup process yet, as I'd like to request these more ancillary changes first and then if all the editors are ready to be tested, I can check at that point.

But it generally looks good and more elegant if it meets the needs of all of our editors, and if the issues I raised can be addressed.

[jfhenon]

I haven't dived too deeply into the details of the Rollup process yet, as I'd like to request these more ancillary changes first and then if all the editors are ready to be tested, I can check at that point.

But it generally looks good and more elegant if it meets the needs of all of our editors, and if the issues I raised can be addressed.

Yep, this was my intention to have a brief feedback from you. This will also takes some time before I can complete this.

[brettz9]

The change to import sounds good if it will work (I can't remember why I didn't go this route). See my other comments.

[jfhenon]

The change to import sounds good if it will work (I can't remember why I didn't go this route). See my other comments.

I'm still struggling to find a way to configure Rollup properly for old browsers (nomodule). I think I progress slowly. I'm more familiar with webpack so would you have an issue if I test it on this one?

[brettz9]

Ugh--I'm sorry but Webpack really has struck me the times I've had to use it as unnecessarily complex, and that seems to be a common view. Webpack also doesn't support ESM distributions--only ESM source.

What nomodule issue are you looking to address? One useful plugin is https://github.com/rollup/plugins/tree/master/packages/replace (or some other third party Rollup plugins that do replacing) which you might use to strip out some input in one build or another, though that is for within JS only I think (not sure if any of the HTML/asset plugins do replacements).

[jfhenon]

Ok. Let's stick to Rollup.