nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

La version 2.0.0-beta.5 ne se charge pas

ChadHutcherson

Notre application utilisait la branche 1.0 de esri-leaflet qui a été supprimée (nous avons toujours un fork de celle-ci) et j'essaie de tout mettre à jour vers la dernière version. J'ai des problèmes pour charger une build de 2.0.0-beta.5 dans leaflet. Je peux construire (en exécutant la tâche grunt) sur une branche créée à partir du tag 2.0.0-beta.5. Le fichier esri-leaflet.js se charge dans l'application, le fichier contient la date de build et la version correctes, mais il ne se charge pas dans l'objet L. L.esri est toujours indéfini. Cela se produit à la fois dans mon application et dans les pages d'exemple. J'ai suivi les 'Development Instructions' et j'ai également essayé les packages npm avec les mêmes résultats. Y a-t-il des instructions que j'aurais manquées ou peut-être un problème avec 2.0.0-beta.5 ? Toute aide est appréciée.<\/P>

Trouver plus de publications taguées avec

Esri Leaflet

Accepted answers

JohnGravois

yeah, sorry about all the confusion. i know exactly whats going on.

i am in the middle of making some fairly broad sweeping changes to the website and the master branch is currently expecting that you'll insert your own build of the compiled source in order to run the site locally.

you have two options:

1. make the same changes in the commit below locally to ensure that you are pointing at the CDN instead.

start using esri leaflet cdn · Esri/esri-leaflet@dc3b1c0 · GitHub

2. place your own new build inside site/build/js/

the tl;dr is that now we are using grunt only for building/running the documentation site. in order to compile the source code locally, all you need to do is call 'npm run build'.

i expect thats clear as mud. let me know if you have any other questions.

All comments

ChadHutcherson

That worked to get the local website running, thanks. The point of getting the local website running was so that I could confirm that 2.0.0-beta.5 was working with leaflet 1b and I see that it is.

So, the real problem I'm trying to solve is that we've built an app using the latest version of leaflet (0.8 at the time) and esri leaflet 1.0 branch (now deleted). The app is angularjs and requirejs plus the angular-leaflet-directive. If I use the old esri-leaflet 1.0 branch build, L.esri is defined but if I load a build of 2b5, L.esri is not defined. I can step through the esri-leaflet initialization code and know it's loaded along with leaflet 1beta2. Did a change take place when moving to esri-leaflet 2 that would cause problems when using requirejs? It looks like somehow it's not being initialized to L.esri. I'm wanting to move to latest because I want to use panes for control of layer zindex and it looks like that was added a while back.

JohnGravois

yeah, sorry about all the confusion. i know exactly whats going on.

you have two options:

1. make the same changes in the commit below locally to ensure that you are pointing at the CDN instead.

start using esri leaflet cdn · Esri/esri-leaflet@dc3b1c0 · GitHub

2. place your own new build inside site/build/js/

the tl;dr is that now we are using grunt only for building/running the documentation site. in order to compile the source code locally, all you need to do is call 'npm run build'.

i expect thats clear as mud. let me know if you have any other questions.

ChadHutcherson

Thanks for your quick help on this John.

Before posting and after trying to get this working for a few hours, I removed my node/npm install (it was working no problem in other projects) and reinstalled. Before I posted the question, I was running npm install but was not running 'npm run build'. Leaflet 1 beta has been loaded in all attempts. I can also change out 2.0.0-beta.5 for the previous 1.0 branch in our app and L.esri is defined.

I just ran npm cache clean, npm install and npm run build. After that, grunt and go to http://localhost:8001/examples/simple-dynamic-map-layer.html and see that it can't find esri-leaflet.js

The sample files tries to load the esri-leaflet.js file but cannot find it:

I see a built file in /dist/

The built js file has this at the top and when building, during npm run build and grunt there are no console warnings or errors:

/* esri-leaflet - v2.0.0-beta.5 - Mon Aug 24 2015 16:09:34 GMT-0500 (CDT)

* Apache-2.0 */

Any ideas?

JohnGravois

have you run 'npm install' recently? the prerequisites required to compile the source code have changed significantly in our last couple refactors. if you have, can you confirm that you are running 'npm run build' to compile the source now? because we don't use grunt for that anymore.

lastly, are you sure you're attempting to load esri-leaflet 2.0.0 alongside the new 1.0 beta of Leaflet itself? i only mention this because our live website still shows samples that point at 0.7.3.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.