component-library | easy way to create HTML styleguide | Awesome List library

It's my first time creating a typescript react npm module, and I am trying to import one of the type definitions in my project that is using the new npm module. VSCode intellisense is able to find and suggest the one of the automatically generated .d.ts files, but the application fails to load it. What is going on?

I have successfully installed Storybook for Vue, but it doesn't seem to handle Vue 3 components very well.

I believe this is because the Vue version is @vue/cli 4.5.11 when I run "vue -V" & the Storybook is 6.1.17 when I run "start-storybook -V"

I don't get how this works. Am I on Vue 3? How do I get Storybook to understand my Vue 3 components?

Here is my package.json file:

I am exploring making a component library using React and rollup, but finding that the app that is consuming the library is bundling it in the wrong order.

This is causing the below error:

I'm trying to import a package into my Rails 6 project – I'm on Rails 6.0.3.4 and webpacker 5.2.1 gem.

• The package is installed yarn add @shopify/react-form
• It's imported into the file import {useForm, useField} from '@shopify/react-form';
• Now after running ./bin/webpack-dev-server

I get this:

I have the following component:

I have created a small component-library for myself based on this GitHub Repo: https://github.com/sveltejs/component-template

This works fine and i have uploaded it to npm.

When i want to use my components in another project i just install them and use them. This works fine as well. The only thing i don't get is Intellisense for the exported properties of my component in VSCode.

What do i have to add in my component library to get some basic Intellisense in the project where i use them?

I'm creating a component library based on Emotion and Typescript.
However, when I import the component in a different project with EmotionJS and NextJS, it doesn't accept the Theme prop.

This is the components repo:
https://github.com/wilsonmsalberto/emotionjs-component-library

This is the repo where I'm reproducing the error:
https://github.com/wilsonmsalberto/emotionjs-component-library-nextjs

My goal is to use the component repo to have multiple themes and multiple components.

Then, in any EmotionJS project, I would import the theme and any component and use it as normal with Emotion.

I'm building directly into the repo and calling the generated component directly from git.

Currently, I'm getting the following error

I've been working on creating a small library of React components for use in several other projects. I am publishing the package internally (using a private GitHub repository) and then including in another project. However, when I go to import from a subdirectory of the package I am not able to do so as the paths don't match.

The projects using the package all utilize webpack to bundle/transpile code as I am trying to avoid doing any building in the component library if possible.

I am trying to pass an argument back to my component library that is imported in a parent app as a dependency, but I am not entirely sure how to achieve this and I was hoping somebody could tell me what am I doing wrong. The idea is that on customer login we will determine which brand are they with and switch the theme that should be used going forward (I added a simplified example rendering a SpecialComponent)

Currently I have a Theme object in my component library that returns a Theme component wrapped in ThemeProvider. This was working fine until I tried to expand the concept of the theme object and add a concept of a brand.

Here is my Theme.js: