- Follows on from
- https://github.com/rancher/dashboard/pull/6603
- https://github.com/rancher/dashboard/pull/6700
- To track messages the console methods were overwritten
- When the console methods were called, we would track message and then call the original console method
- Output into the standard browser console window was broken though
- the inline stack trace for all logs is the place where the original console method is called
- this was always `console.js`
- This causes issues whilst in development but also for logs coming from customers
- Investigate ways around this, but couldn't find anything nice
- short term solution is to remove the feature
- white page errors should not be visible in prod
- these were were enabled in all envs via the port of shell/initialize/client.js after nuxt
- that came from the output of a template
- the template has some features on via debug state when built
- we now disable these features in prod
- Additionally..
- set some process values that were being skipped but still used
- always log uncaught errors in `fetch`s. in theory we should be monitoring $fetchState.error but we never do. this has led to some painful debugging with customers
- fix for isSingleProduct
- two link elements on page, we set the second one, browser showed first one
- not sure why this worked in normal mode
- two link elements on page, we set the second one, browser showed second one
Dai Yuzeng
Richard Cox
Cody Jackson
Giuseppe Leo
Phillip Rak
codyrancher