* Removing everything related to scrollTrigger.
The latest vue router seems to behave exactly as it does with the modified scrollBehavior so it can all be removed.
* Removing unused $nuxt.{suffixes} that I found
- routeChanged (didn't find any watches of this event)
- nbFetching (The only place reading this was a computed property which wasn't used anywhere)
* Replace the use of Vue[installKey]
* Removing some ssr rehydration code since we're not doing ssr
* Remove the remaining $nuxt.$on,$off,$emit and replace with the use of our primary store which already had related code
* Replacing usages of the .$nuxt on vue instances with globalApp references
* Removing SSR dead code
* Fixing an issue where extensions could still be referencing window.$nuxt. This now provides a deprecation warning.
* Migrating another $nuxt over to the window.$globalApp
* Removed the usage of Vue.config.$nux
* Removed the usage of Vue.util.defineReactive
- Saw that the Nuxt component wasn't needed any longer so I removed it instead of trying to work around Vue.util.defineReactive
* Re-run missing check
---------
Co-authored-by: cnotv <giuseppe.leo@suse.com>
* remove ssrcontext arg from createapp function
* remove all mentions to beforeRenderFns and ssrContext + bonus to remove another function related to ssr
---------
Co-authored-by: Alexandre Alves <aalves@Alexandres-MacBook-Pro.local>
- 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
Phillip Rak
Francesco Torchia
Cody Jackson
codyrancher
Alexandre Alves
Evgeniya Vashkevich
Neil MacDougall
Dai Yuzeng
Richard Cox
Giuseppe Leo
codyrancher