search

jquense / react-big-calendar

gcal/outlook like calendar component
http://jquense.github.io/react-big-calendar/examples/index.html
MIT License
7.81k stars 2.23k forks source link

create-react-app 5.0 failed to parse source map #2086

Open popuguytheparrot opened 2 years ago

popuguytheparrot commented 2 years ago

What's the current behavior?

WARNING in ./node_modules/react-big-calendar/lib/css/react-big-calendar.css (./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[2]!./node_modules/source-map-loader/dist/cjs.js!./node_modules/react-big-calendar/lib/css/react-big-calendar.css)
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/node_modules/react-big-calendar/src/sass/variables.scss' file: Error: ENOENT: no such file or directory, open '/node_modules/react-big-calendar/src/sass/variables.scss'
 @ ./node_modules/react-big-calendar/lib/css/react-big-calendar.css 8:6-254 22:17-24 26:7-21 58:25-39 59:36-47 59:50-64 61:4-74:5 63:6-73:7 64:54-65 64:68-82 70:42-53 70:56-70 72:21-28 83:0-224 83:0-224 84:22-29 84:33-47 84:50-64

"react-big-calendar": "0.38.2",

sdumjahn commented 2 years ago

I have the same errors for multiple files.

Using react-scripts 5.0.0 and sass 1.44.0

bezchristo commented 2 years ago

Getting the same issue after moving to webpack5 and react-scripts 5

ivanfuzuli commented 2 years ago

+1

Prince890840 commented 2 years ago

Compiled with problems:X

ERROR in ./node_modules/react-big-calendar/dist/react-big-calendar.esm.js

Module build failed (from ./node_modules/source-map-loader/dist/cjs.js): Error: ENOENT: no such file or directory, open 'D:\Booking\booking (1)\booking\node_modules\react-big-calendar\dist\react-big-calendar.esm.js'

Prince890840 commented 2 years ago

How can I resolve this issue..? can anyone help to reach the solution..?

bartvanandel commented 2 years ago

How can I resolve this issue..? can anyone help to reach the solution..?

I have a feeling this is a different issue than what this thread is about. But to answer your question: does this file exist at all? Have you run npm install?