You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// some functions on `globalThis` that the inspector could call
103
+
// since the inspector can't import modules from a built app.
103
104
importSync('@ember/inspector-support');
104
105
}
105
106
```
106
107
107
108
### No replacements.
108
109
109
-
Applies to both the value and type exports (if applicable).
110
+
Applies to both the value and type exports (if applicable). All of these will not be re-exported from other `@ember/*` packages, but the following tables will show addon usage[^why-addon-usage] in the ecosystem and potential paths forward for library authors.
110
111
111
-
- 🫣 `Ember._getPath`
112
-
- 🫣 `Ember.isNamespace`
113
-
- 🫣 `Ember.toString`
114
-
- 🔒 `Ember.Container`
115
-
- 🔒 `Ember.Registry`
112
+
[^why-addon-usage]: Addons are notorious for doing things they shouldn't, accessing private APIs, doing crazy things so users don't have to, working around ecosystem and broader ecosystem problems etc. It's also expected that addon authors will be able to handle migrations more quickly than app devs.
|🔒 |`Ember.Container`| EmberObserver: [Many, but old or docs](https://emberobserver.com/code-search?codeQuery=Ember.Container)| n/a |
121
+
|🔒 |`Ember.Registry`| EmberObserver: [Many, but old or docs](https://emberobserver.com/code-search?codeQuery=Ember.Registry)| n/a |
116
122
117
123
Internal decorator utils
118
124
- 🫣 `Ember._descriptor`
@@ -136,7 +142,7 @@ Mixins
136
142
Utility
137
143
- 🫣 `Ember.lookup`
138
144
- 🌐 `Ember.libraries` -
139
-
App authors could choose to use any webpack or other build plugin that collections this information, such as [webpack-node-modules-list](https://github.com/ubilabs/webpack-node-modules-list). This additionally means that V1 libraries that pushed themselves into `Ember.libraries` no longer need to worry about interacting with this or any similar API.
145
+
App authors could choose to use any webpack or other build plugin that collections this information, such as [webpack-node-modules-list](https://github.com/ubilabs/webpack-node-modules-list) or [unplugin-info](https://github.com/yjl9903/unplugin-info). This additionally means that V1 libraries that pushed themselves into `Ember.libraries` no longer need to worry about interacting with this or any similar API.
140
146
- 🫣 `Ember._Cache`
141
147
- 🔒 `Ember.GUID_KEY`
142
148
- 🔒 `Ember.canInvoke`
@@ -165,7 +171,6 @@ Utility
165
171
- 🔒 `Ember.generateGuid`
166
172
- 🌐 `Ember.uuid`
167
173
- 🔒 `Ember.wrap`
168
-
- 🫣 `Ember.deprecateFunc`
169
174
- 🔒 `Ember.inspect`
170
175
- 🫣 `Ember.Debug`
171
176
Replaced by some of `@ember/debug` exports.
@@ -244,6 +249,7 @@ Most of this is covered in [RFC #176](https://rfcs.emberjs.com/id/0176-javascrip
0 commit comments