ember-cli / ember-cli/ember-cli-app-version
App version in Ember console debug statements
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Just started using this in our app, so thanks :smile:
Since the addon defines an initializer that registers the app as an ember library, I was surprised to see that it wasn't listed in the normal [library version debug output](https://github.com/emberjs/ember.js/blob/v1.11.0-beta.4/packages/ember-application/lib/system/application.js#L1106-L1126). After a little digging it appears that initializers run after [that method is called](https://github.com/emberjs/ember.js/blob/v1.11.0-beta.4/packages/ember-application/lib/system/application.js#L282), so the app version isn't in the list when it's printed. Not a big deal, but I've definitely found it handy to find the version in the console without opening the ember inspector and clicking the info tab (I used to call `Ember.libraries.register` in `app/app.js` directly).
I would have opened a PR, but I can't figure out how to use addon hooks to run code before `Ember.Application#init` is called. The only thing I could think of was to add an inline script using the `contentFor` hook, but that ends up violating CSP. Do you have any idea how to do this?
Contributor guide
Research direction
Start with the linked Ember application.js sections showing the library debug output and the Application#init call order. Read the addon's initializer and contentFor hook behavior, along with the existing app/app.js registration approach. Done means the app version appears in the normal console library output without violating CSP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100