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
The same as 👆🏻works for src/core/public and kibana/public. In both cases we are able to import types only. If something like the kibanaResponseFactory is imported that path needs to specify the full relative prefix to the location of the server or public folder otherwise a module not found error prevents Kibana from starting.
Are we planning on collapsing these aliases into one? (why have two ways of doing the same thing)
Should we be importing "concerete" things like kibanaResponseFactory from core as described above?
The text was updated successfully, but these errors were encountered:
The same as 👆🏻works for
src/core/public
andkibana/public
. In both cases we are able to import types only. If something like thekibanaResponseFactory
is imported that path needs to specify the full relative prefix to the location of theserver
orpublic
folder otherwise a module not found error prevents Kibana from starting.kibanaResponseFactory
from core as described above?The text was updated successfully, but these errors were encountered: