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

Optional transformation, maybe use as babel macro #93

Open
DimaRGB opened this issue Feb 20, 2020 · 4 comments
Open

Optional transformation, maybe use as babel macro #93

DimaRGB opened this issue Feb 20, 2020 · 4 comments

Comments

@DimaRGB
Copy link

DimaRGB commented Feb 20, 2020

Question:

Is it possible to make this plugin work as macro, like preval ?

Problem:

In some files i need to use default dynamic import().
And i want to have some mechanism to enable the transform plugin only for some files, maybe even only for some cases.

@DimaRGB DimaRGB changed the title Use as babel macro Use as babel macro? Feb 20, 2020
@DimaRGB DimaRGB changed the title Use as babel macro? Optional transformation, maybe use as babel macro Feb 20, 2020
@cdoublev
Copy link

Might be fixed by #134.

@ScriptedAlchemy
Copy link
Collaborator

Looking for maintainers on the universal suite. A significant amount of time is dedicated to module Federation and webpack 5 - this would near eliminate the need for Babel transformers this substantial.

@cdoublev
Copy link

I read your post(s) about it. It sounds very interesting. I didn't realize it could fill this space (code transformers). I'm not sure if I can take any new responsibilities with your universal packages. I'm already struggling to do enough work on my own to be honest + I'm not 100% fluent in english. But I can help when I can. This is the minimum I can do in return of accessing those great packages for free.

(Sorry to pollute this issue).

@ScriptedAlchemy
Copy link
Collaborator

Yeah no problem. And your PRs are appreciated! Until a point in time where there's a crossroads of needing to rebuild the universal toolset - it still does what's it needs to.

The only part I might update would be universal component. But that would be a breaking change. Moving universal to a module federation based system since it's far superior and covers the basics of what universal did.

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