Module parse failed: Unexpected token patronum.umd.js
Open
question
- Dominant language
- TypeScript
- Stars
- 312
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
Optional chaining `?.` on many places of code
```javascript
p({ type: t, name: o, scopeName: n?.name, value: e });
```
patronum@1.12.3
Contributor guide
Research direction
Start by inspecting the published patronum.umd.js from patronum@1.12.3 and reproduce the reported parse failure using the optional-chaining example. Trace the package entry point or build configuration that produces this bundle; done means the distributed UMD module parses successfully in the affected environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100