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

fix(utils): [Edge 18] ensure function prototype #440

Open
wants to merge 2 commits into
base: v5
Choose a base branch
from

Conversation

buschtoens
Copy link
Collaborator

Fixes #417.

Apparently (starting with Edge 18?) Edge's JS engine performs some broken optimizations for the return value of decorator. The returned function somehow gets stripped off its Function prototype and instead gets Object.

This fix ensures the Function prototype for Edge.

@mfeckie
Copy link

mfeckie commented Apr 30, 2019

Are there any blockers to getting this merged? (awesome that you've found a workable fix)

@buschtoens
Copy link
Collaborator Author

CI is acting up for unrelated reasons for the ember-beta and ember-canary build, it seems. I restarted them, but they still fail. ember-cli-dependency-checker for some reason cannot find the ember-data package. It might not be installed.

I'll try to fix this later today. Then somebody with npm publish access (@rwjblue and @pzuraq) can publish.

@mfeckie
Copy link

mfeckie commented Jun 3, 2019

How we going here peeps?

@pzuraq
Copy link
Contributor

pzuraq commented Jun 19, 2019

@mfeckie sorry, it just hasn't been a priority since we have a lot of work to do to ship decorators/tracked properties upstream, and the recommendation is to upgrade to v6 which shouldn't have this issue 😕 If Jan can get tests passing and handle the deployment, I'm 👍 on landing this, but I'm not going to have time to look into it myself.

@buschtoens
Copy link
Collaborator Author

Unfortunately we already migrated all of our apps to v6 as well. 🙊

@mfeckie
Copy link

mfeckie commented Jun 20, 2019

Yeah, I think that's what we're likely to do ... time permitting :)

@rwjblue
Copy link
Contributor

rwjblue commented Aug 9, 2019

Just wanted to clarify here, this PR targets the v5 branch but I'm not 100% sure why? Is it only applicable to v5?

@buschtoens
Copy link
Collaborator Author

@rwjblue that is correct. This issue only occurs with v5.

@kiwi-josh
Copy link

Hey folks, is there any chance we could get some movement on this? 🙏 I would be more than happy to help out where possible if time is the main blocker.

@pzuraq
Copy link
Contributor

pzuraq commented Sep 5, 2019

@wytlytningNZ unfortunately none of the maintainers have time to work on this issue, since it doesn't affect the current major release. Our recommendation is to upgrade to v6.

If you would like to take over this PR and get tests passing, that would be really helpful. At the least it would mean you could pin your package.json to a commit, if we still don't have time to merge and publish a patch version.

@buschtoens
Copy link
Collaborator Author

You can also use this hotfix: #417 (comment)

But I can only reiterate on @pzuraq's point. Rather try upgrading to v6 as quickly as possible, to avoid being locked in to and old and unmaintained state of the Ember ecosystem.

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

Successfully merging this pull request may close these issues.

None yet

7 participants