-
-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to parse source map from '~/node_modules/rrule/src/cache.ts' file: Error: ENOENT: no such file or directory, open '~/node_modules/rrule/src/cache.ts' #522
Comments
Having exactly the same issue. Running on Arch |
Aha, this makes sense actually. The generated sourcemaps are simply a statement-by-statement mapping from the output in the npm bundle (dist/) to a source file under src/, and the src/ isn't published in the npm bundle, so naturally it isn't found! I'll experiment with some other build settings and see what I can come up with. |
See this relevant discussion here: googleapis/google-cloud-node#2867 |
Wouldn't be simple as including src into the files in the package.json?
|
@davidgoli Do we have any solution figured out for this issue? I'm facing the same issue and for now, I have fixed it by adding |
@davidgoli Any progress with this? I can't add "GENERATE_SOURCEMAP=false", as we actually do need our own source maps. Thanks for your work on this library. It's a huge help! |
Experiencing the same issue. Any update please? |
Experiencing the same issue. |
Same here unfortunately. |
if you still want it in your Development, you can create a new file called |
same error :( |
same 👎 |
@davidgoli Sorry for the direct / late ping, but did you figure out any solution? |
I went with GENERATE_SOURCEMAP=false which was ok in my case |
I'm experiencing same error and also cannot use "GENERATE_SOURCEMAP=false" as a fix |
Is this still not fixed? :( |
This issue is still in version 2.7.2. Workaround for me also:
|
+1 |
I've just created this PR to resolve the issue -- I've tested and it works locally: #593 |
+1 |
You probably don't want to turn off source map generation for your entire project, but you can suppress the source map warnings from rrule and get a clean build. The solution described here worked great for me: facebook/create-react-app#11767 (comment) I used the following config:
|
Where you have added it? |
@IvanGrekov Check out the comment I referenced. I did it the way they described. |
@davidgoli if the source maps are broken should the source maps just be turned off by changing the I'd be happy to open a PR and test it out if you think that's an acceptable approach for the time being. I don't think I'm knowledgable enough to do the full solution discussed in that google cloud thread you linked. |
could a solution be using yarn? |
I just tried adding the rrule library and I'm getting the same issues about failed to parse source map for [x] files. Any update? |
Reporting an issue
Thank you for taking an interest in
rrule
! Please include the following inyour report:
creating a new one
are using such as the exact RRule string and dates.
I am using create-react-app
version 5
with webpackversion 5
, and on creating the build i am getting warings as shown belowShould work without failing on generating the source maps
The version of
rrule
you are usingversion
2.7.0
Your operating system
Linux (Ubuntu 21.04)
Your local timezone (run
$ date
from the command lineof the machine showing the bug)
```
Mon 13 Jun 2022 04:33:28 PM +08
The text was updated successfully, but these errors were encountered: