Windy - Errors in lib.js started on 1st August
-
Hi Windy,
We first noticed we were getting errors from lib.js this morning, errors shown in Chome Dev Console:
Can you please investigate this?
Let me know if you need any more information. We were not getting these errors last week.
Euan
-
Hi @CompassDSNM ,
sorry for the issue, we will look into this.Can you please specify, how and what parameters are you setting up? It looks like the problem is with product and overlay.
If you don't want to enclose details here, write us an email to support@windy.com
Thanks,
Tomas -
-
@nesro said in Windy - Errors in lib.js started on 1st August:
I can see that you released a new version at 9am this morning. Before that we had no issues.
The errors before were when we were using an older version of libboot.
Using your updated version of libboot.js we get the following:
I think the error is happening when we are adding controls to the map, but it is hard to know exactly.
const options = { key: 'ourKey', verbose: false, zoom: 3, }; function SetupMap() { try { localwindy = windyInit(options, windyAPI => { const { map, picker, utils, overlays, store, broadcast, particles } = windyAPI; map.removeLayer(W.labelsLayer); MapState = new MapStateManager(map); map.MapState = MapState; map.addControl(L.control.zoom({ position: 'topleft' })); //more code } }
-
@compassdsnm thank you for reporting this issue. In order to fix this, is it possible to get access to a running example? I could debug it and find out the problem.
I see that your page is protected by a login so I cannot try it.
-
@nesro I have emailed a login to support@windy.com
-
@compassdsnm
We encountered the same bug. windy is set up to work on a standard single page website. To get it to work with angular we had to fix it to run with a local copy of libboot.js stuck on an old reliable version 23. Recently, about Aug 1st I would say, their wind overlay stopped working with version 23. We encountered the same params failed error when entering the weather map.The libboot.js at windy is now on version 36. It does not work with angular.
We had to hack and kludge. Finally by some miracle we got it to work.So anyway, since your page is protected by login, you are probably using some sort of modern mainstream framework to run your website. You are going to have to hack and kludge to get version 36 to work for you in your setup. Then the error goes away.
-
@ovwindy Also be aware that the latest version 36 appears to have a bug. gl-particles stopped working after upgrade to 36. L.CanvasLayer is not defined in the right place and this causes a DI error when adding @plugins/gl-particles The error messages and symptoms look like a require error.