create-react-library | CLI for creating reusable react libraries | Frontend Framework library

I'm trying to create a customisable ReactJS component library. I've considered create-react-library for the purpose. Component development is almost finished. I've placed all my components in separate directories, and I'm exporting all of them in one go, with the help of an index.js. All components have associated local scss files as well. These component level scss file takes reference from another variables.scss which has scss variables like,

$primaryColor: #ff0000;

$secondaryColor: #000000;

There are 2 parts to this question.

1. Is there any way to not compile the scss into one css when we publish the package. Currently create-react-library is compiling all the scss into a folder named dist as index.css, which doesn't give the option to update styles from parent project with scss variables.

2. Once the issue with scss compilation is solved, how can we update these variables from a parent project (where developers will be using the package created).

Any sort of help is much appreciated.

I'm trying to create a React library npm package for import into other modules.

The package uses redux and the intention is to expose the reducer, so that it can be loaded by the consuming application.

I've used create-react-library to construct the basic library infrastructure.

In simplified terms, my structure is as below. The full repo can be seen here.

Library application

I've got some browser sniffing code that I'm using inside of a react component

I'm trying to publish to npm a React component I created , so I found about the create-react-library and is my first time that I'm using it , I'm trying to test my component from the test folder that it comes with the create-react-library and it compiles successfully but my browser is showing

Fragment is not defined

when I use the <> fragments of React

the package.json of the Test folder look like this:

I created a new project with create-react-library. I am trying to add a unit test using Jest and Enzyme. My test works for a simple component, but Jest fails to test a component that references semantic-ui-react.

This test works:

I'm writing a React component library which I want to use in other projects without much overhead ( bit, create-react-library, generact, etc. ) and without publishing. I want to use npm install ../shared_lib to add it to my project as a symlink in /node_modules. This command adds the symlink to project node_modules. In my shared_lib I just have a test to export default a

I will start to develop a react that will be used by many internal react apps in my company. This library is starting from scratch, and there are many architectural decisions to be made about the components, utilities, REST client API, etc. To facilitate the development, the idea is to develop the library in parallel with the first react app.

For now, I created the library using create-react-library and deployed it in our internal Nexus 3 repository using npm publish. Also, I already created the react app using the create-react-app. During the development, I will start to watch the react app, and I want that every modification made on the library or in the app should be synchronized in the react app server.

My question is: How I can link locally the react library and the react-project, in such a way that I only start the react-project (npm start)?