-
-
Notifications
You must be signed in to change notification settings - Fork 236
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 ... #831
Comments
I confirm we still have this issue with version 7.1.1 of |
rehype-mathjax@4.0.3 create a warning on the LTI build, a .map is missing in a dependency of the package. Dowgrading to 4.0.2 fix the issue. The dependency having this issue is parse5. An issue is open on their github repo: inikulin/parse5#831
rehype-mathjax@4.0.3 create a warning on the LTI build, a .map is missing in a dependency of the package. Dowgrading to 4.0.2 fix the issue. The dependency having this issue is parse5. An issue is open on their github repo: inikulin/parse5#831
rehype-mathjax@4.0.3 create a warning on the LTI build, a .map is missing in a dependency of the package. Dowgrading to 4.0.2 fix the issue. The dependency having this issue is parse5. An issue is open on their github repo: inikulin/parse5#831
rehype-mathjax@4.0.3 create a warning on the LTI build, a .map is missing in a dependency of the package. Dowgrading to 4.0.2 fix the issue. The dependency having this issue is parse5. An issue is open on their github repo: inikulin/parse5#831
rehype-mathjax@4.0.3 create a warning on the LTI build, a .map is missing in a dependency of the package. Dowgrading to 4.0.2 fix the issue. The dependency having this issue is parse5. An issue is open on their github repo: inikulin/parse5#831
rehype-mathjax@4.0.3 create a warning on the LTI build, a .map is missing in a dependency of the package. Dowgrading to 4.0.2 fix the issue. The dependency having this issue is parse5. An issue is open on their github repo: inikulin/parse5#831
fyi @fb55 this is because the we could either stop generating sourcemaps in prod, or just ship them. what do you think? |
Source maps reference the original TypeScript files. Most of my packages reference the source files on GitHub (example, longer explanation), which I couldn't figure out how to do with the monorepo setup of parse5. I would prefer to ship useful source maps, but if that isn't possible, removing the reference seems logical. |
I am using parse5 in a react app, and the modules are referring to a sourceMap file that is not being found, which is interrupting the build of the app.
I can confirm checking the dist/index.js in npm
Line 45
//# sourceMappingURL=index.js.map
however, there isn't such file relative to path
The text was updated successfully, but these errors were encountered: