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

Embroider addon compatibility #9536

Closed
25 of 29 tasks
thoov opened this issue May 18, 2021 · 6 comments
Closed
25 of 29 tasks

Embroider addon compatibility #9536

thoov opened this issue May 18, 2021 · 6 comments
Labels

Comments

@thoov
Copy link
Contributor

thoov commented May 18, 2021

This issue tracks embroider compatibility across the top section of addons in the community with the goal of getting help from others to improve embroiders compatibility. We have created test helpers that can be added to addons to validate that they work in embroider in both safe and optimized variants via ember-try scenarios. Below is a list of the top 25 addons (according to emberobserver.com) and their current state. If you are able to work on adding @embroider/test-setup (instructions can be found here) please reference this issue so I can keep this list updated.

@NullVoxPopuli
Copy link
Contributor

has this list been updated? I think more of these are compat now?

@bertdeblock
Copy link
Contributor

@NullVoxPopuli I've updated the list as best as I could, please let me know if anything else should be checked off.

@NullVoxPopuli
Copy link
Contributor

Some of these can't be v2 addons, and maybe may never need embroider compatibility?

Like ember-cli-postcss is often used with Tailwind, and the ideal tailwind setup works best with webpack-native plugins (or as a separately running build)

And the polyfills... should be easy tests.

@bertdeblock
Copy link
Contributor

bertdeblock commented Aug 26, 2022

Does ember-angle-bracket-invocation-polyfill need to be Embroider compat?
Angles are fully supported in Ember v3.10+, so might be overkill?

@bertdeblock
Copy link
Contributor

Is this issue still needed / relevant?

@bertdeblock
Copy link
Contributor

bertdeblock commented Jan 31, 2023

I updated the list a bit more, but going to close this for now. I think for the most part, this ticket has served its use.
I suggest specific tickets are created in the appropriate repo's if needed.

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

No branches or pull requests

3 participants