-
Notifications
You must be signed in to change notification settings - Fork 6
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
Remove ember-rfc176-data
patch
#1
Comments
I opened ember-cli/ember-rfc176-data#322 to add the mapping. |
While we are waiting for #1, this will allow us to actually publish a functional, albeit über-hacky, first release. 🚀
Unfortunately it seems that (at least with I tried patching the package in function patchRFC176Data() {
const mapping = require("ember-rfc176-data");
const hasMemoMapping = Boolean(mapping.find(
(m) => m.module === "@glimmer/tracking" && m.export === "memo"
));
if (hasMemoMapping) return;
mapping.push({
global: "Ember._memo",
module: "@glimmer/tracking",
export: "memo",
deprecated: false,
});
} However, this does not work, as |
Seems like another option is to add an Another, possibly much cleaner option could be adding this export to |
Hmm, when installing this locally via yarn, it worked, without applying the patch I believe. (at least the import did not work, I used it directly from
I did nothing but |
Yeah, it seems that I would like to find some hack to completely avoid it. The most probable solution would be disabling the transpilation of the I can push and release a fix, that would at least disable the |
That would work for me, at least :) So if that is OK, then I'd be all for that! |
I've removed It's released in For reference I also raised ember-cli/babel-plugin-ember-modules-api-polyfill#133 to improve the underlying infrastructure for future polyfills. |
The required
Ember._memo
mapping for{ memo } from '@glimmer/tacking'
has not yet been added toember-rfc176-data
. This is why we usepatch-package
to patch this in, just so we can get our feet off the ground. For a "stable" release, we need to remove this hackery and land the required change upstream.These commits need to be reverted:
The text was updated successfully, but these errors were encountered: