[CAUTION] Support wider range of browsers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 194
- Avg merge
- 18m
- Merged PRs (30d)
- 3
Description
A proposal not to use the newer language syntax without polyfill, or to protect against exceptions. My Sentry got an error from the Umami script. On Chrome 83, an exception occurred with a missing formal parameter error. I haven't had this happen with tianji yet, but since you're taking a cue from Umami, I'm letting you know that I've had this happen and that you should be careful about supporting only newer browsers.
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 reviewing the TypeScript browser-facing code and the linked Umami issue for the reported Chrome 83 “missing formal parameter” exception. The issue is done when the Tianji script avoids the unsupported syntax or handles the exception and works on the browser range the project intends to support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100