purescript / purescript/trypurescript
Proposal: Add the es-optimizer as an option for ShowJS
Nobody has claimed this yet.
- Dominant language
- PureScript
- Stars
- 121
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
A lot of times I use the ShowJS tab to do a quick-and-dirty performance evaluation of PS code before I use it in a repo. These days, almost all of my repos are using the es-optimizer, so my quick-and-dirty flow no longer works. I'm wondering if it's too much trouble to wire up the backend optimizer to trypurescript as an option?
Contributor guide
No contributing guide indexed for this repository
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 locating the ShowJS tab and the backend optimizer integration in trypurescript. Determine how optimizer choices are currently represented and whether es-optimizer can be exposed as an option. Done means the ShowJS performance-evaluation flow can use es-optimizer.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100