Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failed to parse source map #48

Open
tvogelsang opened this issue Dec 27, 2021 · 2 comments
Open

Failed to parse source map #48

tvogelsang opened this issue Dec 27, 2021 · 2 comments
Assignees
@joelnet
Labels
enhancement New feature or request

Comments

@tvogelsang
Copy link

tvogelsang commented Dec 27, 2021 •
edited
Loading

Added @paciolan/remote-component to a CRA app, done in JS (not TS) receiving the following when using webpack:

Failed to parse source map from 'C:\...\node_modules\@paciolan\remote-component\src\components\RemoteComponent.ts' file: Error: ENOENT: no such file or directory, open 'C:\...\node_modules\@paciolan\remote-component\src\components\RemoteComponent.ts'

Receiving this error on about 15 different .ts files that do not exist in the npm package.
@joelnet
Copy link
Member

joelnet commented Jan 2, 2022

Hmm. I'll have a look at this.

@joelnet joelnet added the enhancement New feature or request label Jan 2, 2022
@joelnet joelnet self-assigned this Jan 2, 2022
@ttessarolo
Copy link

I've the same problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joelnet joelnet

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@joelnet @ttessarolo @tvogelsang