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

Can experimental feature from Next.js 'externalDir' replace this plugin completely or do we still need it? #203

Closed
matiishyn opened this issue May 12, 2021 · 2 comments

Comments

@matiishyn
Copy link

I'm sorry I don't keep the format, but this is just a question hopefully in the right place

I've just scrolled down to this comment
vercel/next.js#9474 (comment)
and looks like it should do the job.
So, my question is, Can this replace the externalDir replace the next-transpile-modules plugin completely or do we still need it?

@martpie
Copy link
Owner

martpie commented May 12, 2021

I saw this new thing in a next.js commit, but I did not investigate more than that, so the answer is: idk.

It may replace common scenarios like transpiling a module for IE11 or dealing with monorepos, but I don't think it'll cover things like transpiling CSS or enabling HMR, but this is just me speculating.

@martpie martpie closed this as completed May 18, 2021
@donsn
Copy link

donsn commented Sep 4, 2021

I saw this new thing in a next.js commit, but I did not investigate more than that, so the answer is: idk.

It may replace common scenarios like transpiling a module for IE11 or dealing with monorepos, but I don't think it'll cover things like transpiling CSS or enabling HMR, but this is just me speculating.

It supports HMR. But I'll use this till 'externalDir' is no longer an experimental feature

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