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

Polyfill throws an error when linking locally #42

Open
ramitha opened this issue Jun 30, 2021 · 0 comments
Open

Polyfill throws an error when linking locally #42

ramitha opened this issue Jun 30, 2021 · 0 comments

Comments

@ramitha
Copy link

ramitha commented Jun 30, 2021

The following named blocks error is seen when an app that is on ember-source<3.25 (i.e. no support for named blocks) and is dependent on an addon that uses named blocks.

/home/nballamb/li-work/talent-solutions-web/hue-web-datepicker/components/hue-web-datepicker.js: Assertion Failed: Named blocks are not currently available, attempted to yield to a named block other than "default" or "inverse": yield to="textInput". ('hue-web-datepicker/components/hue-web-datepicker.hbs' @ L51:C4)

Workaround for linked MPs at this point is to use the flag USE_NAMED_BLOCKS_POLYFILL=true while starting up the app.

Note: ember-named-blocks-polyfill needs to be a dependency in both the addon and the app (dev).

I'm guessing this has to do with the fact that we're using versionChecking to determine if the polyfill should be used or not and that has issues when its locally linked. Wondering if we could check for the block name instead and use the polyfill if it is a named block.

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

1 participant