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.
v1.5.0 regression - No File Matching error
See original GitHub issueRepo: https://github.com/jzs11/vite-regression-playground
run npm i and npm run build
You shall be able to see the following error:
Downgrade to v1.4.0 the problem is gone.
Thanks!
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Error change in 1.5.0 when adding a file that doesn't exist · Issue ...
ENOENT error would be returned. We used this to handle the case where the file may or may not exists, e.g.: err =...
Read more >How to Fix: Error in eval(predvars, data, env) : object 'x' not found
This error occurs when you attempt to use a regression model in R to predict the response values of a new data frame,...
Read more >docker - no matches for kind "Replicaset" in version "apps/v1"?
My minikube version: v1.26.1. I couldn't figure, whether the issue is with my code or api resources. this is my error: resource mapping...
Read more >Possible regression in v1.11.4 to 1.12.x - very high CPU ...
Till v1.11.4, things seem to be working all fine, but on v1.12.0 or v1.12.1, I am seeing extremely high CPU usage (4000%) on...
Read more >Troubleshoot Azure Log Analytics Linux Agent - Microsoft Learn
A regression in nss-pem package v1.0.3-5.el7 caused a severe ... DSC resource logs class not found error in omsconfig.log log file.
Read more >
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
sorry i made a mistake, updated to 1.5.1 will fixed.
I had the same issue, and confirmed Downgrading resolved the issue as well. Thank you!