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
{{ message }}
This repository has been archived by the owner on Dec 13, 2019. It is now read-only.
An uber package is essentially the same as the structure of the git repo, with the added dist folder with the generated outputs for umd and esm.
We'd like to publish the uber packages under the @dojo scope. For example: dojo-has (umd) ---> @dojo/has (uber).
The work to add this to the release task is trivial, but one thing we must deal with is switching the dojo dependencies in the package.json (which are the umd ones) to use the uber equivalents, so that in effect, when you pull an uber package down from npm you will get any of the dependencies of it in uber form also.
The text was updated successfully, but these errors were encountered:
@matt-gadd I am not sure this reflects our current thinking and is unactionable in its current state. I maybe wrong, and if I am, we should clarify the scope of this issue.
An
uber
package is essentially the same as the structure of the git repo, with the addeddist
folder with the generated outputs forumd
andesm
.We'd like to publish the
uber
packages under the@dojo
scope. For example:dojo-has
(umd) --->@dojo/has
(uber).The work to add this to the release task is trivial, but one thing we must deal with is switching the dojo dependencies in the
package.json
(which are the umd ones) to use the uber equivalents, so that in effect, when you pull anuber
package down from npm you will get any of the dependencies of it inuber
form also.The text was updated successfully, but these errors were encountered: