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.

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

How it can support sourcemap for third party libarary installed node_modules #256

Closed
tianyingchun opened this issue Feb 9, 2022 · 3 comments

Comments

@tianyingchun
Copy link

Are you trying to transpile a local package or an npm package?
@dimjs/utils

Describe the bug
how it can support sourcemap for third party libarary installed node_modules

i tried install thrid party libarary in node-modules in next app, import function from node_modules it seems it could not load source map file in chrome, e.g. i. have module file is-null.js & is-null.js.map the is-null.js.map indicates the source ts file.

but it can not display is-null.ts in chrome sources panel. is there missed some configuratins?

To Reproduce
see vercel/next.js#34026

Expected behavior
see vercel/next.js#34026

Setup

  • Next.js version:
  • next-transpile-modules version: latest
  • Node.js version:
  • npm/yarn version: npm 8
  • Operating System:
  • Webpack 4 or 5: 5

Additional context
next 12

@ronenempathy
Copy link

having the same issue .

any workaround found around that?

@martpie martpie closed this as completed Jun 18, 2023
@ronenempathy
Copy link

why is this closed?

@martpie
Copy link
Owner

martpie commented Jun 19, 2023

cf. #291

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants