Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Graduating experimentalWatchApi from experiment to default
See original GitHub issue👋 After reading up on https://github.com/TypeStrong/ts-loader/pull/685 and some related issues that had cropped up over the course of testing, I wanted to ask:
- What would it take to graduate
experimentalWatchApifrom an experimental API to the default watch behavior forts-loader? - Are there any lingering known issues with it? (I didn’t find anything from a cursory search.)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:17 (9 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
False alarm @johnnyreilly. The issue still occurs without the experimentalWatchApi. It’s safe to assume our problem was unrelated. Dragons indeed.
We are not using webpack 4 yet on our projects, but I’ll check when we find some time to migrate haha