Drew Baker

OK so if I create a Nuxt plugin, and then add `Vue.config.devtools = true` to it, DevTools will work. But if I add the following to my `nuxt.config.js` file, DevTools...

My `.nuxt-storybook/client.js` file has the following in it: ``` // Try to rehydrate SSR data from window const NUXT = window.__NUXT__ || {} const $config = NUXT.config || {} if...

Mystery deepens. If I use a Nuxt plugin to log out `context.isDev` it is `true` so still no idea what is stopping Vue devtools....

I got a workaround in the meantime, using a Nuxt plugin like this: ``` import Vue from "vue" export default function ({ isDev }) { Object.assign(Vue.config, { devtools: isDev })...

> I confirm the bug but not the workaround. Still impossible to inspect the code with devtools (FF or Chrome) in the storybook iframe embed or the standalone view too....

I'm also very confused with how we are supposed to use SVG's in CSS with this?

I wonder if we should just make a page `search` that we use for all search results? I've always thought it was weird how you could do a search on...

This is what he wants: https://wordpress.org/plugins/admin-post-navigation/

It might be a dead plugin though

I don't think we want to fetch data client side, the SEO hit would be bad as I understand it. I know what you mean by the `$programmed_routes` mapping to...