eslint-loader | A ESlint loader for webpack | Code Analyzer library

craco's Github readme, states that it is supporting Create React App (CRA) 4.*. By this statement, I'm assuming CRA 5 is not officially supported by craco.

However, this repository utilizes both CRA 5 and craco (but I have not verified that it is working). Use this repository to compare your setup (after verifying that the linked repositry is working), and try different settings/configs to see if you get further.

You need to keep react installed, unfortunately. It's required by react-scripts for starting the dev server and is unavoidable without forking the package.

If you're concerned about the alias working with React still being installed, you can comment out your config and compare build sizes. You should see a sizable difference, confirming your alias works as intended.

It had to with the webpack version

The solution was to add the line in the Dockerfile:

I had the same problem with literally the exact same number of vulnerabilities.

Check out the solution here

Depends on how complex your application will get. One option is two-way data-binding as explained here: https://v3.vuejs.org/guide/component-basics.html#using-v-model-on-components

So you basically emit the changes to the parent.

For more complex applications I wouldn't pass data that are used in multiple components as props, but use a store. Either a simple reactive object; with provide/inject or use something like Vuex.

The documentation of the vue-splide integration is clearly talking about Vue3 composition API.

Checking in the github issues of vue-splide, I found this one which is referencing a solution that you've linked above. Meanwhile, when trying this, those are the warnings that I do have in my CLI.

Those are also related to Vue3 (which is not compatible with Nuxt2, only Nuxt3 supports Vue3). Looking at the date of all the posts, it looks like it was matching somewhat the time-frame when Vue3 was still in a beta-limbo and probably not adopted by everybody.

At some point, I guessed that the package maybe lost some retro-compatibility with Vue2 in the next months. I then tried to install the version 0.3.5 of @splidejs/vue-splide rather than the latest one and it's working perfectly fine with it!

Here is the whole setup to have it working with Nuxt2 nuxt.config.js

Try in your Dockerfile to set

Since you are using create-react-app for this, there's no need to eject the webpack.config.js (since this is irreversible, I hope you have a git commit you can revert). So here's the general gist:

• You create a file called chatLoader.js outside of your react project (if you don't intend to learn how to configure this in the same webpack config, which might get a little tricky) and add babel transpilation and minification by yourself.
• This file contains something like (untested)

The issue was solved by bumping storybook to the latest stable version aka 4.1.0 as shown here: https://github.com/nuxt-community/storybook/releases

Nuxt was pretty much the latest already.