design-system | 🗃 Storybook Design System | Frontend Framework library

A better approach is to create your own theming in nebular instead of changing individual elements according to your need, but there is a way to achieve what you're trying as well.

To do that you'll need to find the classes related to the stepper, and then apply your styling in your global styling files

NOT in the component styling. That won't work as nebular has global styling set up and it will override your styling, even if you use !important

You can use the following classes for updating the stepper:

1. .nb-theme-corporate nb-stepper .header .step.selected .label-index

   This is for updating border/background colors for selected step

2. .nb-theme-corporate nb-stepper .header .step.selected

   This is for changing font styling for selected step

For all other steps, you just need to remove .step.selected and it will be applied

As stated in the comments, using the import is mixing module formats.

I got it working with the following configuration.

I figured out what the issue. For some reason, the dist folder was not being generated for me every time I ran npm run build.

Sometimes it was generated, other times it wasn't. I believe it was due to some errors in my component code, which failed silently. So now I check for the dist folder every time I build the library.

In my final, working attempt I went with the monorepo approach as advised by the Stencil team in their documentation.

Here are all I took the steps for a basic Stencil library with a React output:

• Create a monorepo
• Create a Stencil Library
  • Generate components using npx stencil generate
  • Update name in package.json to MY_LIBRARY
  • npm i @stencil/react-output-target
  • Add the React Wrapper function to stencil.config.ts

TL;DR: The inline source map is kinda broken, it's a bug in carbon-preprocess-svelte.

When you use: import { Tile } from 'carbon-components-svelte', the default module resolution will import the named export Tile from a big umbrella file at carbon-components-svelte/lib/index.js, which is a big minified code bundle. Clearly this is not optimal.

optimizeImports from carbon-preprocess-svelte is a preprocessor that tries to optimize it by reading your import code then rewriting it into sth like import Tile from "carbon-components-svelte/src/Tile/Tile.svelte".

Obviously there's some kind of bug in this preprocessor, that produces a broken source map. To be precise, it produces a source map that misses out some mapping positions. Chrome devtool relies on these mapping positions to set a breakpoint. When it's missing, it cannot set one.

When you manually rewrite the import, you skip this preprocessor, thus you avoid the wrong behavior. This is consistent to your current finding.

We might rest our case here and conclude that you should avoid using optimizeImports for now, and just report the bug to carbon team. Below will dive into more details.

This is the inline source map of the bad case:

The loadChildren should load "design-system.module.ts" not the "design-system-routing.module", is the design-system.module who import "the design-system-routing.module"

As you can see in Shadowing in Gatsby themes docs:

This feature allows users to replace a file in the src directory that is included in the webpack bundle with their own implementation. This works for React components, pages in src/pages, JSON files, TypeScript files, as well as any other imported file (such as .css) in your site.

The shadowing API uses a deterministic file structure approach to know which component should or shouldn't be rendered. In your case, you just can override the CSS props to display it as none, or you just shadow and return an empty component, since shadowing is used to extend Gatsby themes. Create a src/gatsby-theme-blog/components/Switcher/Switcher.js in your project and do something like:

you can use a hook for initialize your stringVal before the request..

I've had a similar issue when developing a component library using storybook and emotion/styled-components. The issue was that I was using the styled-components' ThemeProvider from the consumer app, as you did in your _app.js. The solution was to create and export a custom ThemeProvider on the component library, using the library's styled-component package, like so:

Unfortunately, standard WPF controls don't provide an "official" way to implement the acrylic and reveal highlight effects.

You can try using third-party libraries for this. For example DevExpress controls, which include both acrylic and reveal highlight features: Fluent Design Support.

The screenshot below illustrates what you can get:

You can download this example at How to Create a Unique Design for a WPF View using Appearance Options.

Another possible solution is to use the FluentWPF package.