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.
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=truewhile 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.