Unknown feature "default-async-observers" found in config/optional-features.json

[ozywuli]

Unknown feature "default-async-observers" found in config/optional-features.json

An error occurred in the constructor for @ember/optional-features at /Users/<username>/projects/<project_name>/node_modules/semantic-ui-ember/node_modules/@ember/optional-features

An error occurred in the constructor for semantic-ui-ember at /Users/<username>/projects/<project_name>/node_modules/semantic-ui-ember

Seeing this error on a fresh install of ember-cli@3.17. Any ideas why?

[Unkrass]

I'm having the same issue. I believe that it is not a Semantic-UI-Ember specific issue, but rather Ember-CLI related.

https://guides.emberjs.com/release/configuring-ember/optional-features/#toc_default-async-observers

I opened an issue in the ember-cli repo here

[kulbida]

Wondering if you were able to find a solution, yet.

[Unkrass]

@kulbida unfortunately no. I‘m still waiting for a response in the ember-cli repo issue I mentioned in my above comment.

[Unkrass]

I have to backpedal. This really is an issue with semantic-ui-ember. When removing the package from package.json it works just fine...

[Unkrass]

Well, @richard-viney just showed me that it's an issue with the @ember/optional-features dependency inside semantic-ui-ember. So, please someone bump this to 1.3.0.

Until then you can use the following workaround with selective dependency resolutions in package.json (on the same level as dependencies):

"resolutions": {
  "semantic-ui-ember/@ember/optional-features": "^1.3.0"
}

For further information on resolutions check https://classic.yarnpkg.com/en/docs/selective-version-resolutions/

[richard-viney]

@Unkrass Could you open a PR that fixes this?

[Unkrass]

@richard-viney I have opened a PR

[palyvodaBoi]

seems it doesn't work..

[FrancoisLetourneau]

There's a PR that was never merged regarding this issue.

Can we expect a resolution soon?

[richard-viney]

My workaround above should continue to work fine. There's not much else to be done except wait for a maintainer to bump the package version and/or merge that small PR.

[allthesignals]

Please bump

[RubenSmit]

Could this please be resolved? The solution is fine indeed, it only needs to be merged and the version bumped.

[zubeirom]

Well, @richard-viney just showed me that it's an issue with the @ember/optional-features dependency inside semantic-ui-ember. So, please someone bump this to 1.3.0.

Until then you can use the following workaround with selective dependency resolutions in package.json (on the same level as dependencies):

"resolutions": {
  "semantic-ui-ember/@ember/optional-features": "^1.3.0"
}

For further information on resolutions check https://classic.yarnpkg.com/en/docs/selective-version-resolutions/

Thats only working with yarn, for npm please use npm-force-resolutions https://www.npmjs.com/package/npm-force-resolutions