unfixable deprecation issue [deprecation id: ember-string.add-package]
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start with the deprecation message and the project's package.json, comparing the declared @ember/string devDependency with the imports that trigger the warning. Review the linked Ember deprecation guidance and referenced ember-string issue to determine whether the warning or dependency resolution is actionable. Done means identifying a confirmed fix or documenting why the issue must wait for Ember internals to change.
Written by the indexing model from the issue text.
Description
DEPRECATION: Importing from `@ember/string` without having the `@ember/string` package in your project is deprecated. Please add `@ember/string` to your `package.json [deprecation id: ember-string.add-package] This will be removed in ember-source 5.0.0. See https://deprecations.emberjs.com/v4.x/#toc_ember-string-add-package for more details.
After upgrading to ember 4.10, I noticed that I am seeing thousands of this deprecation warnings when my app boots up. I checked and to my surprise I was having "@ember/string": "^3.0.1" within devDependencies in my package.json. A discussion on discord pointed be to @ef4 comment: https://github.com/emberjs/ember-string/issues/235#issuecomment-1061413761
Looks like this is describing a similar issue, where it is unclear which implementation (ember-string vs ember internals) is being used.
Is there anything that can be done other waiting for ember to remove its own implementation, or manually silence deprecation warnings?
Additionally it looks like in this case the deprecation message is quite misleading - however, I guess that is part of ember and not ember-string?
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from emberjs/ember-string
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
emberjs/ember-string#447 · 40 comments · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
emberjs/ember-string#253 · 1 comment ·
All issues in emberjs/ember-string
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·