Repository navigation
Possible issue with webpack path resolver after migrating to v.5.0.0 #11838
Description
Hello cra team,
We have mono repository with 4 project and components library. We use yarn worspace to symlink components dependecy to project.
Components library is built with rollup. TS and CSS are compiled into bundles. Also we are copiing scss variables to dist for reusing it in projects.
We import styles and scss variables to projects from node_modules using alias like this
import "~components/dist/style.css"
import "~components/scss/variable"
Everything works fine on 4.0.3, but after migarting to 5.0.0 looks like something wrong with path resolver in webpack.
We also have tried without ~, as it is deprecated in sass, but result is still the same.
Also we are not able to load some JSON files in typescript module from "components/dist/some.json"
We are using react-scripts with typescript, seems like exports property in package.json is still experimental for typescript.
We have already tried all of the simple solutions like re-install of the node_modules.
Could you please assist?
Activity
stanlaktionov commentedon Jan 4, 2022
Any updates on this?
haworku commentedon Jan 4, 2022
I'm seeing this same issue with not being able to find scss stylsheets after upgrade
Also have tried
bstaruk commentedon Feb 3, 2022
I was having this same issue and solved it by:
SASS_PATHtoREACT_APP_SASS_PATHin.env(ex:REACT_APP_SASS_PATH=./node_modules;./src)@import,@use, etc... for example,@import 'style/variablesbecomes@import 'style/_variables.scss.After making these changes I was back in business with CRA v5 (upgrading from v4).
furmandev commentedon Mar 1, 2022
Experiencing this issue as well.
Changing imports from
@use 'variables'to@use 'src/styles/_variables.scss'removes the warning, but this is not ideal IMOhaworku commentedon Apr 4, 2022
I was able to also fix my issue by using full paths as described ^