etn-ccis / blui-cli Goto Github PK

Describe the desired behavior

Only use the RNC Cli to build React Native projects

Describe the current behavior

Allows selection of RNC or Expo

Is this request related to a current issue?

No

Additional Context

We're not really recommending people to use Expo for production applications. We were using it in some cases because Expo projects can run in snack, but with the growing complexity of our packages and the stripped down way of doing dependency management in Snack, that no longer works. So there doesn't seem to be much benefit in continuing to support this in the CLI.

Describe the desired behavior

pxb new --lint=false should not install any lint & prettier

Describe the current behavior

As long as you have a --lint flag, lint will be installed; otherwise, it won't.

Is this request related to a current issue?

May want to do this while working on #16 .

Additional Context

This is an issue after #15 is merged

Describe the desired behavior

CLI should use NPX for the CLI commands

Describe the current behavior

Current behavior assumes that the individual framework CLIs are globally installed on the local machine.

Is this request related to a current issue?

No

Additional Context

Using NPX will also ensure that we are always using the latest version of the particular CLI

Describe the bug

The CLI doesn't stop after generating new project. This results in the end user having to press cmd+c before entering any other commands.

What is the expected behavior?

The CLI should stop after a new project is generated so the end user can immediately enter an additional command

What are the steps to reproduce?

1. Generate any new project via the CLI as detailed in the current CLI documentation
2. Observe the CLI hanging at the end of new project generation

Screenshots / Screen recording

Describe the desired behavior

Templates have to blank routing or authentication

Describe the current behavior

Docs do not mention this and can be interpretted as the package used instead.

Is this request related to a current issue?

No

Additional Context

Describe the desired behavior

CLI should automatically include our linting profiles and commands.

Describe the current behavior

No linting is in the repositories by default.

Is this request related to a current issue?

No

Describe the bug / expected behavior

React Native projects generated with the BLUI CLI do not build properly

What are the steps to reproduce?

1. Generate a new @brightlayer-ui/cli react native project from the dev branch
2. Run project via yarn ios or yarn android
3. Observe build failing

Screenshots / Screen recording

Code snippet / Link to minimum reproduction example

ios build fail message

** BUILD FAILED **


The following build commands failed:
	CompileC /Users/<redacted>/Library/Developer/Xcode/DerivedData/TestAuth-fzujnhijaatcjuenpivjtugfrouo/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/RNReanimated.build/Objects-normal/arm64/UIResponder+Reanimated.o /Users/<redacted>/etn-ccis/test/TestAuth/node_modules/react-native-reanimated/ios/native/UIResponder+Reanimated.mm normal arm64 objective-c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'RNReanimated' from project 'Pods')
	CompileC /Users/<redacted>/Library/Developer/Xcode/DerivedData/TestAuth-fzujnhijaatcjuenpivjtugfrouo/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/RNReanimated.build/Objects-normal/arm64/NativeProxy.o /Users/<redacted>/etn-ccis/test/TestAuth/node_modules/react-native-reanimated/ios/native/NativeProxy.mm normal arm64 objective-c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'RNReanimated' from project 'Pods')
(2 failures)

error Command failed with exit code 1.

Android build fail message

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':tasks'.
> Could not create task ':react-native-pager-view:compileDebugAndroidTestKotlin'.
   > Cannot use @TaskAction annotation on method AbstractKotlinCompile.execute() because interface org.gradle.api.tasks.incremental.IncrementalTaskInputs is not a valid parameter to an action method.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 10s
error Failed to install the app.

Your environment information

Suggested fix

Anything else to add?

Describe the desired behavior

To run pxb cli and create a new repository with all branches and files from a windows system.

Describe the current behavior

pxb new repository fails at SED steps. (only empty repo is created)

• pxb new repository
  Repository Name: » test
• Repository Name: · test
  This project demonstrates how to: » cli repo test
  This project demonstrates how to: · cli repo test
• Creating Repository
• Repository Created
• Creating Temp Folder
  Temp Folder Created
• Preparing Template Files
  — Something went wrong (1)
  Command failed: cd temp_1579548378661 &&
  git clone https://github.com/pxblue/example_template example_template
  sed -i "" "s/[repository-name]/test/g" ./example_template/README.md
  sed -i "" "s/[PROJECT NAME]/Test/g" ./example_template/README.md
  sed -i "" "s/...[DESCRIPTION]/ cli repo test/g" ./example_template/README.md
  sed -i "" "s/[REPOSITORY-NAME]/test/g" ./example_template/.circleci/config.yml

The syntax of the command is incorrect.

Additional Context

when each sed is run without double quotes no syntax error is observed.
(sed -i "s/[repository-name]/test/g" ./example_template/README.md)

Tried running pxb cli from cmder terminal and also tried Cygwin utility with same results.
https://cmder.net/
https://cygwin.com/

Describe the bug

The default app-test for RN template projects fail due to not having safe-area wrapper for when the header is rendered in test.

What is the expected behavior?

test to pass with default test file

What are the steps to reproduce?

1. Start new RN blank project - npx -p @pxblue/cli pxb new
2. Open project and run yarn test

Screenshots or links to minimum reproduction example

Environment

Anything else to add?

The issue can be fixed via the CLI project or in the templates repo.
The test file should have...
import { SafeAreaProvider } from 'react-native-safe-area-context';

• and with

Describe the bug

README needs to show on the npm page here:
https://www.npmjs.com/package/@pxblue/cli?activeTab=dependencies

What is the expected behavior?

README is available without going into the github repo.

What are the steps to reproduce?

https://www.npmjs.com/package/@pxblue/cli?activeTab=dependencies

Describe the desired behavior

More robust tests in CircleCI:

• Unit tests for the commands and extensions
• Build verification to ensure that the changes and files we expect are correct after a build
• Confirm that the created projects are able to be run successfully

Describe the current behavior

We only have unit tests for the help and default commands and e2e tests to verify that the CLI builds and can create projects in each framework.

Is this request related to a current issue?

No

Describe the bug

After the CLI runs, when printing the instructions for running on Android, the cd step is missing.

What is the expected behavior?

The first step in the Android instructions should be to cd into the project directory we just created.

The instructions should be:

• Have an Android emulator running
• cd
• yarn android

What are the steps to reproduce?

1. clone this repository
2. yarn && yarn build && yarn link
3. blui new react-native
4. Respond to the prompts to create a new react native project
5. After the project is created, observe the printed instructions for Android. The cd step into the project is missing.

Screenshots or links to minimum reproduction example

Anything else to add?

The instructions are correct for running on iOS. We should be able to reference that in order to make this update.

Describe the desired behavior

Include the font files and guard by default in a new RN project.

Describe the current behavior

Currently this (lengthy) step has to be done manually despite being identical for all of our projects.

Is this request related to a current issue?

No

Describe the bug

It worked before but today when I was trying to use the cli for a ts project, it gives me the following message on yarn start:

Welcome.

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
USMOOWWM543G8WN:cli-test-ts c3050144$ yarn start
yarn run v1.17.3
$ react-scripts start
/Users/c3050144/Documents/pxblue/cli-test-ts/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:239
      appTsConfig.compilerOptions[option] = value;
                                          ^

TypeError: Cannot assign to read only property 'jsx' of object '#<Object>'
    at verifyTypeScriptSetup (/Users/c3050144/Documents/pxblue/cli-test-ts/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:239:43)
    at Object.<anonymous> (/Users/c3050144/Documents/pxblue/cli-test-ts/node_modules/react-scripts/scripts/start.js:31:1)
    at Module._compile (internal/modules/cjs/loader.js:956:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
    at Module.load (internal/modules/cjs/loader.js:812:32)
    at Function.Module._load (internal/modules/cjs/loader.js:724:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)
    at internal/main/run_main_module.js:17:11
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

But the same steps with a js flag does not induce any error and works like normal.

What is the expected behavior?

No error.

What are the steps to reproduce?

1. npx -p @pxblue/cli@beta pxb new react --name cli-test-ts --lint --prettier --language ts --template blank
2. yarn start
3. (Error message as listed above)

Screenshots or links to minimum reproduction example

N/A

Environment

MacOS, node v12.13.0

Anything else to add?

Describe the bug / expected behavior

Typescript license url is broken
https://github.com/Microsoft/TypeScript/raw/master/LICENSE.txt

What are the steps to reproduce?

1. clone the repo
2. Open LICENSES.json
3. Click on licenseUrl / open in browser

Screenshots / Screen recording

Code snippet / Link to minimum reproduction example

CODE HERE

Your environment information

Suggested fix

Replace the url with https://github.com/Microsoft/TypeScript/raw/main/LICENSE.txt

Anything else to add?

Describe the desired behavior

When generating a new angular project using pxblue linting, the tslint.json should not show up in the root directory

Describe the current behavior

It both installed pxblue/eslint-config and generated a tslint.json in the project files.

Describe the desired behavior

When starting a new react native project using the RNC CLI, the project should be ready to go with SVG icons out of the box.

Describe the current behavior

Currently, the default project is not configured to allow the use of SVG icons, so copying and pasting code snippets that includes icons will give you the red screen of death.

Is this request related to a current issue?

Discovered when testing the new version of the RN component library.

Additional Context

We need to include packages for:

• react-native-svg
• react-native-svg-transformer
• @types/react-native-vector-icons (dev dependency for typescript projects)

Then we need to follow the steps for configuring react-native-svg-transformer (https://github.com/kristerkari/react-native-svg-transformer#step-3-configure-the-react-native-packager)

Describe the desired behavior

Use Angular 13, React 17, MUI v5 and update other dependencies used by the CLI

Describe the current behavior

These dependencies are out of date

Is this request related to a current issue?

No

Additional Context

Some of these dependencies may already be handled by updates to the templates themselves, but we should check to see what else there is that is specified in the CLI and need to be updated.

Describe the bug

When starting an Angular project created with the CLI, the console throws a bunch of yellow warnings about TSConfig (spec files etc.).

What is the expected behavior?

No warnings for a fresh project:

What are the steps to reproduce?

1. npx -p @pxblue/cli pxb new angular
2. Use default options
3. Start the fresh project
4. Observe the warnings in the console

Screenshots or links to minimum reproduction example

Anything else to add?

Seems to be an issue somewhere in our "Add PX Blue" functionality. Creating a project with the Angular CLI runs without warnings.

Describe the bug

Currently, the cli react typescript will include

        "@testing-library/jest-dom": "^4.2.4",
        "@testing-library/react": "^9.3.2",
        "@testing-library/user-event": "^7.1.2",

in package.json's dependencies field

What is the expected behavior?

Should have anything for dev only under devDependencies

What are the steps to reproduce?

1. Generate react typescript project
2. Check package.json

Screenshots or links to minimum reproduction example

package.json from this commit:
pxblue-components/documentation@10c9871

What is your environment?

Framework

• Angular
• React
• Ionic
• React Native

Browser

• Internet Explorer
• Edge
• Safari
• Chrome
• Firefox

Operating System

• MacOS
• Windows
• Other

Anything else to add?

Describe the bug

We are currently using the 'ionic' package from npm to scaffold new ionic projects, which is deprecated.

What is the expected behavior?

We should be using @ionic/cli instead

Environment

Anything else to add?

Describe the desired behavior

The CLI should prevent project names that will ultimately throw errors in the underlying CLI.
All three frameworks that we support, Angular, React & RN, have their own unique project name requirements.

Describe the current behavior

If an invalid name is provided, the user is still prompted for all questions. When attempting to make the project it will throw an error since project name invalid.

Is this request related to a current issue?

No

Additional Context

You'll need to look up the specific naming rules for each framework as the rules for Angular are not the same as the rules for RN, etc.

Describe the desired behavior

We need a --prettier flag separate from the --lint flag to install js & ts respectively.

Describe the current behavior

--lint install both prettier and lint, but for ts projects only

Is this request related to a current issue?

No

Additional Context

Raised during the sprint review on #15.

Describe the desired behavior

Remove Expo option for RN projects

Describe the current behavior

CLI allows you to choose between RNC and Expo CLI for RN projects

Is this request related to a current issue?

No

Additional Context

Make sure to update the documentation / Readme as well.

Describe the desired behavior

The CLI should be able to work behind a proxy. It should allow users to configure their proxy settings if applicable.

Describe the current behavior

CLI must be run on a network without a proxy.

Is this request related to a current issue?

No

Additional Context

The upstream issues that this depends on (gluegun) seem to be updated and capable of supporting this feature now.

Describe the bug

npm render the markdown slightly differently from GitHub

What is the expected behavior?

Should have no "\|" in the table

What are the steps to reproduce?

1. Go to https://www.npmjs.com/package/@pxblue/cli
2. check the readme file

Anything else to add?

We had that problem between GitHub vs storybook before... need to figure out a universal solution for all three of them

Describe the desired behavior

Need to lock down branches to contributors only by default when creating a repository

Describe the current behavior

Branches are wide open

Is this request related to a current issue?

Related to the security vulnerabilities identified by evan

Describe the desired behavior

CLI template selection should be limited to supported templates. This applies to angular and react projects.

Describe the current behavior

Users can enter whatever template they want through the --template flag.

Is this request related to a current issue?

No

Additional Context

Describe the desired behavior

Code in the new projects should be linted in accordance with our package rules (and use 4 spaces when writing back to the JSON files).

Describe the current behavior

Code is not linted (2 spaces used in JSON).

Is this request related to a current issue?

No

Describe the desired behavior

Remove Ionic option from framework selection

Describe the current behavior

Ionic is an option

Is this request related to a current issue?

No

Additional Context

Make sure to update the documentation / Readme as well.

Describe the bug

When using the CLI to create a new repository, the ionic branch doesn't have the network_security_config.xml

What is the expected behavior?

File should be included

What are the steps to reproduce?

1. pxb new repository delete-me
2. config file is not present in the ionic branch

Anything else to add?

The script should be running the ionic cordova resources command before pushing to github (which it appears to be doing). The gitignore file also does not include this config file, so it should be getting added...something funny is happening in the process.

Describe the bug / expected behavior

installing the Blui cli global throws warnings on some dependencies that should be upgraded.

What are the steps to reproduce?

1. yarn global add @brightlayer-ui/cli
2. observe the warnings.
3. Not 100% sure but the warning on tar-pack might have a security issue as well
4. The local node version is 16.20.0

Screenshots / Screen recording

yarn global add @brightlayer-ui/[email protected]
yarn global v1.22.19
[1/4] 🔍 Resolving packages...
warning @brightlayer-ui/cli > react-native-asset > [email protected]: Version 1.x or earlier is no longer supported.
warning @brightlayer-ui/cli > create-react-app > tar-pack > [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
warning @brightlayer-ui/cli > react-native > jest-environment-node > @jest/fake-timers > @sinonjs/[email protected]: Use version 10.1.0. Version 10.2.0 has potential breaking issues
warning @brightlayer-ui/cli > react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
warning @brightlayer-ui/cli > react-native > @react-native-community/cli > @react-native-community/cli-plugin-metro > metro > metro-minify-uglify > [email protected]: support for ECMAScript is superseded by uglify-js as of v3.13.0
warning @brightlayer-ui/cli > react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: https://github.com/lydell/resolve-url#deprecated
warning @brightlayer-ui/cli > react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: See https://github.com/lydell/source-map-url#deprecated
warning @brightlayer-ui/cli > react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: Please see https://github.com/lydell/urix#deprecated
[2/4] 🚚 Fetching packages...
warning [email protected]: The engine "yargs" appears to be invalid.
[3/4] 🔗 Linking dependencies...
warning "@brightlayer-ui/cli > [email protected]" has unmet peer dependency "@types/node@".
warning "@brightlayer-ui/cli > [email protected]" has unmet peer dependency "[email protected]".
warning "@brightlayer-ui/cli > react-native > [email protected]" has unmet peer dependency "@babel/core@".
warning "@brightlayer-ui/cli > react-native > [email protected]" has unmet peer dependency "react@^16.0.0 || ^17.0.0 || ^18.0.0".
warning "@brightlayer-ui/cli > react-native > [email protected]" has unmet peer dependency "react@^16.8.0 || ^17.0.0 || ^18.0.0".
warning "@brightlayer-ui/cli > react-native > @react-native-community/cli > @react-native-community/cli-plugin-metro > [email protected]" has unmet peer dependency "@babel/core@*".
warning "@brightlayer-ui/cli > react-native > react-native-codegen > [email protected]" has unmet peer dependency "@babel/preset-env@^7.1.6".
[4/4] 🔨 Building fresh packages...
success Installed "@brightlayer-ui/[email protected]" with binaries:
- blui
✨ Done in 22.69s

Code snippet / Link to minimum reproduction example

CODE HERE

Your environment information

Suggested fix

Anything else to add?

Describe the bug

The Expo configuration is broken and will throw a Font Not Found error for material icons and open sans.

What is the expected behavior?

No errors.

What are the steps to reproduce?

1. Spin Up a new Expo project
2. Insert a PX Blue typography element into the App.tsx
3. Run the project
4. Observe the RSOD

Screenshots or links to minimum reproduction example

Environment

expo-cli version 4
iOS (Android fails gracefully and uses a different system font).

Anything else to add?

expo/expo#7552
expo/expo#11333

The fix appears to be to use the @expo/metro-config package instead of adding our own metro configurations for the react-native-svg-transformer. We should remove the metro.config.js that we add here:
https://github.com/pxblue/pxblue-cli/blob/dev/src/extensions/pxblue-extensions.ts#L505

We also need to remove the use-expo dependency:
https://github.com/pxblue/pxblue-cli/blob/dev/src/extensions/pxblue-extensions.ts#L470

And just use expo-font for the useFonts Hook (included with expo dependencies, no need to install anything here):

import { useFonts } from 'expo-font';

Describe the desired behavior

See if we should switch to using Capacitor instead of Cordova.

Describe the current behavior

Using cordova, which appears to no be the preferred approach any longer.

Is this request related to a current issue?

Additional Context

Describe the desired behavior

CLI should work flawlessly with the latest versions of Node and NPM.

Describe the current behavior

The CLI works best with Node 14 and NPM 6. It will work with NPM7 if it's globally installed. When using the latest versions, a lot of things seem to be broken.

Is this request related to a current issue?

This is related to a number of issues that were identified after trying to update to the latest node.

Additional Context

Describe the bug

When I generate a React Native TS lint project, there is an App.js and App.tsx generated in the project root folder.

What is the expected behavior?

Only App.tsx should be generated.

What are the steps to reproduce?

1. npx -p @pxblue/cli pxb new
2. choose React Native, TypeScript, Lint, React Native Community
3. Check the root folder

Screenshots or links to minimum reproduction example

What is your environment?

Framework

• Angular
• React
• Ionic
• React Native

Operating System

• MacOS
• Windows
• Other

Anything else to add?

Describe the bug / expected behavior

The CLI does not automatically exit the initialization process when everything is finished. Users have to manually control-D to exit. I vaguely recall that this was not the case before.

What are the steps to reproduce?

1. npx -p @brightlayer-ui/cli blui new react --name=font-audit
2. I selected "Blank", and "yes" to both ESLint and Prettier

Screenshots / Screen recording

This is 10 minutes after everything has been installed:

Your environment information

macOS 13.3.1

Describe the desired behavior

I want new flags added so I can easily test beta or alpha template packages.

Describe the current behavior

When selecting a template, only the latest version is pulled down.

Is this request related to a current issue?

No

Additional Context

Describe the desired behavior

Use the newest theme (6+) and the updated import syntax for @fontsource/open-sans.

Describe the current behavior

Using the older theme and older typeface-open-sans package.

Is this request related to a current issue?

This is related to typeface-open-sans being deprecated in favor of @fontsource/open-sans. I updated the themes to use the new package, but it's currently just in beta awaiting additional updates to bundle into the new major version. I did not want to publish a new version of this package that makes use of a beta version of the theme. Once the 6.0 version of the theme is published as latest, we can come in here and make the update. Creating this issue so we don't forget.

Additional Context

I made a branch for this (feature/typeface) that you can use.
If we build ionic templates, this may not need to be done in the CLI.

Describe the bug

A new angular project does not include the material icon font in index.html by default

What is the expected behavior?

Should include the link tag with the font import

<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet" />

What are the steps to reproduce?

1. Start a new project
2. Copy over some code that uses mat icons
3. Observe that the icons are just text strings

Screenshots or links to minimum reproduction example

Anything else to add?

This should be a quick update in the template code where we are currently adding the class to the root element to apply the theme.

Describe the desired behavior

Generated RN projects should use the latest React Native package

Describe the current behavior

Generated RN projects are locked down on 0.64.1

Is this request related to a current issue?

Additional Context

Describe the desired behavior

It would be nice to know which version of the template was used when creating a project with the CLI. Perhaps we can add a comment at the top of one of the main copied files that says the version so it's easy to identify during testing, e.g.:

/*
* This project was scaffolded with version x.x.x of the XYZ template
* */

Describe the current behavior

We can't tell what version of the template was used to build a project. We can get a sense if versions are different from each other by looking at the dependencies in package.json, but it's kind of a pain and not very exact.

Is this request related to a current issue?

Related to the testing going on for supporting alpha and beta versions of templates in the CLI.

Additional Context

It would be cool if we could programmatically pull this out of the package.json file so we don't have to remember to update it every time.

Describe the desired behavior

The latest version of react native / react native cli do autolinking via gradle and cocoapods, so we shouldn't need to run the rnlink command anymore. Look at the instructions for RNVI for how to use Cocoapods (we are already using Gradle on the android side). We will need to modify the podfile to add a line and we will need to add a new entry in the Info.plist file too.

Describe the current behavior

Currently we do rnlink to link up fonts for react native vector icons package.

Is this request related to a current issue?

No.

Additional Context

If we can successfully take this out, we may no longer need to include the extra step instructions for removing the duplicate resources and the end of the CLI workflow.

Describe the bug

Right now the cli generates a new babel.config.js, and added "babel-preset-expo": "~8.0.0" to package.json devDependencies.

What is the expected behavior?

These two files should not be generated.
(Update: according to my experimentation at search-bar react native branch, babel config is required for expo to work)

What are the steps to reproduce?

1. install cli globally
2. generate a typescript barebone (for react native)

Screenshots or links to minimum reproduction example

this search-bar commit generates the two thing mentioned above.

What is your environment?

Framework

• Angular
• React
• Ionic
• React Native

Browser

• Internet Explorer
• Edge
• Safari
• Chrome
• Firefox

Operating System

• MacOS
• Windows
• Other

Anything else to add?

Describe the bug

Cannot create a new ionic authentication template with prettier & eslint enabled.

What is the expected behavior?

It works.

What are the steps to reproduce?

1. npx -p @pxblue/cli@ pxb new and select ionic, prettier, auth, eslint options.

Screenshots or links to minimum reproduction example

Environment

Anything else to add?

Windows

Describe the desired behavior

CLI should be more opinionated about dependency versions instead of installing the latest version of everything. Lately, we've seen some incompatibilities with various versions of packages caused by this behavior. We should periodically update these as necessary with subsequent releases rather than trying to eliminate the need for updates by using latest.

Describe the current behavior

Installs latest version of everything.

Is this request related to a current issue?

Yes, projects started with the CLI do not run out-of-the-box for Angular or React.

Additional Context

Add any other context or screenshots about the feature request here.
Angular should be fixed once we release the new version of the component library, react has incompatibilities with the version of eslint required by react-scripts.