Stackflow doesn't work with plain JavaScript modules
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 114
- Avg merge
- 3m
- Merged PRs (30d)
- 2
Description
This framework doesn't work with standard JavaScript module semantic because of a circular dependency on required configuration.
For example in the official example, MyActivity.tsx module and stackflow.ts have circular dependency, which will never work with errors like:
Uncaught ReferenceError: Cannot access 'MyActivity' before initialization
at stackflow.ts:10:5
Or users should use bundlers to inject bundler-specific runtime behavior. That means its behavior is essentially not reliable
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
Reproduce the circular dependency in the official example, focusing on the imports between MyActivity.tsx and stackflow.ts. First inspect how those modules require each other and test the example without a bundler. Done should mean the example works with standard JavaScript module semantics without bundler-specific runtime injection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100