-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
由于roadhog的dev-tool bug官方一直未修复,请教下你们内部是如何进行调试的 #786
Comments
去dva提吧。我都是强行看得 |
强行跟踪 es5 代码~ |
我降级roadhog到1.3.1,这样就可以调试源码了 |
还一个问题是,请求老是返回304,导致无法获取到mock返回的数据。而实际上我直接从浏览器地址访问的时候,又是可以获取到数据的。 |
Closed
umijs/umi#43 ,@pigcan 在看了。 |
这个bug解决了没有?痛苦死了。 |
太痛苦了 |
痛苦 |
这个问题已经修复了,是不是可以关闭了,改一下依赖到最新的@2.3.0-beta.1就行。 |
正式版本发布。主分支升级会关掉的 |
fix in 2009bf3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
由于roadhog的dev-tool 配置的bug官方一直未修复,现在F12都是编译的代码,看的比较吃力,
sorrycc/roadhog#554
请教下你们内部在用这个框架的时候是如何进行调试的?
The text was updated successfully, but these errors were encountered: