mgechev / mgechev/angular-seed
External UMD module is unable to resolve RxJS after prod build
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.5k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
Minko, I know you're a busy guy, but if you have a moment, could you look through this issue I've opened over on the angular2-toaster project? I've got an issue that has stumped me as well as the project creator. I can't tell if it's an issue with his UMD bundle or an issue with the way the seed project maps RxJS for prod builds.
I won't ask you to spend a bunch of time on it, but I figured you might have some immediate ideas just from looking over the symptoms.
https://github.com/Stabzs/Angular2-Toaster/issues/131
Thanks!
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 with the linked Angular2-Toaster issue 131, then compare its UMD bundle behavior with how this seed project maps RxJS for production builds. The work is done when the source of the external module's RxJS resolution failure is identified and the relevant build or bundle behavior is made compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- build-system, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100