unicons | Lightweight textarea behavior for inserting Unicode symbols | Frontend Utils library

you don't have a class named 'show-menu' so adding it to the element would make no effect

As OP said, the answer was to replace all the tags by s (+ SSR and apollo prefetch in his case).

if you visit the link to your stylesheet it appears to be taken offline..

https://unicons.iconscout.com/release/v3.0.1/css/unicons.css

here is the active one:

https://unicons.iconscout.com/release/v3.0.6/css/solid.css

As you can see they have created a paid and free version. This will result in a couple of name changes and/or unusable icons.

But as you can see it does work. I have made a snippet so you can see.

The iconPacks:Unicons element is a markup extension and not a control. Use the PackIconUnicons control instead and bind the Spin property to the IsMouseOver property of the parent button.

The issue is not related to MVVM. Controls in WPF have a visual and logical structure defined in XAML along with states and triggers for those states to change control properties on state changes. This is defined in the control template.

In case of a Button there are states like Pressed, MouseOver or Disabled just to name a few. All of these states have a visual representation. For example, in the Disabled state, the Background will be changed to light grey, and the opacity is reduced. Triggers for that in the control template take precedence over triggers defined in styles, so you need to create a custom control template to change the representation of the Disabled state.

As creating custom control template can be complex, you should copy the default control template or style of a control and adapt it. Be aware that the default template may vary depending on the libraries that you use. In case of MahApps.Metro, you can find the default button style and template here.

The part that you are interested in is the trigger for the Disabled state.

Vue CLI has its own config for sass-loader (and is already doing what you've configured), so the rule that you've added for sass-loader is adding a duplicate processor, where the output of Vue CLI's sass-loader is being fed into yours, causing the error. The solution is to remove your config for module.rules.

Note you're also duplicating a Vue CLI config in resolve.extensions. I recommend using vue inspect to view the project's resolved Webpack config for troubleshooting. It's helpful to diff the output before and after you've made changes.