ECMDERR Failed to execute "git ls-remote --tags --heads https://github.com/Nijikokun/query-js.git", exit code of #128 Host key verification failed. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
@Kiti-Nomad that sounds like an issue with your connection to github
is someone available to help me understand how the build system generally works?
I have some questions about errors I am getting prior to my transformations
I upgraded my Dojo package and util to 1.16.4
I am transforming ES_2017 -> ES3 but when i run the builder, I first get a syntax error on the ES2017 as the builder "processes" the code, and then it transforms it.
So I am unsure if I can ignore that error? I would really like my build log to not contain a bazillion syntax errors when they are transformed later to not be errors
Do you do the es2017 -> es3 as part of the dojo build? We use Babel for this and run the dojo build on the resulting es3 code.
We do have a lot of warnings from the dojo build, though
yeah I have been using it as a part of the dojo build
Hi, I have an existing Dojo (1.16) application. I'm adding Vue on top of it and actually almost everything works with a bit of synchronization between AMD parsing on Dojo's side and component rendering on Vue's side. There's one big issue though: TabContainer renders completely off.
Is there anybody with experience with this combination of libraries? Or any other which also exhibits similar behaviour?
with "completely off" I mean that the hidden elements from the top bar - which are correctly hidden in the version which doesn't wrap the DOM in Vue - are showing as part of the page with the version which uses Vue.
btw, I'm using Vue only for state management and routing in the client side app (for now).
Dijit is still very much the most professional looking widget toolkit out there, IMO.
hi. In the Vue+Dojo integration that posted about on Wednesday, the "dojo/ready" function doesn't work anymore. Does anybody have experience hacking into the dojo/ready mechanism and running the queue when the app is "ready"?
I would like to ask you if somebody could hint me to github source or some documentation where I could find any information about usting relative paths (not component names in define) in data-dojo-type how they are being resolved. I noticed in some cases that they're not resolved relatively to the js component / file which is using that html template. Sometimes it's being resolved in context of dojo/parser module which is very confusing to me.
I know that using relative paths is not the brightest idea in html templates but unfortunately that's not the code I can change too much.
Unfortunately no. I noticed in some propertiary code that "../../shared" something like this works for the 1 component and doesn't work for 2 component even though they're referencing the same component and they're in the same directory