Convert Tortoise to use ES6 modules
Nobody has claimed this yet.
- Dominant language
- CoffeeScript
- Stars
- 57
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Galapagos was converted to use ES6 modules along with Rollup to create minimized code for each page-specific bundle. That has worked well for that project. It would be nice if Tortoise was converted as well, to make it easier to include dependencies that are already updated to ES6 modules. Some considerations for the switchover:
- Generating a minimized version as well as a maximized version with full variable names and whitespace.
- Enabling the dynamic import of extensions as modules instead of their current state as statically included in the engine.
- Possibly swapping the final published artifacts from webjars to a standard npmjs package.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Galapagos pull request and Tortoise’s current build and packaging setup. Map how extensions are statically included and how webjars are published; done means agreeing on and implementing the ES6-module conversion, minimized and readable bundles, dynamic extension imports, and the package publication approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript, javascript, rollup
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100