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
When I use npm link to load the layer-selector into another local project on my machine, I get strange error messages in the console like this:
Accessor#set Assigning an instance of 'esri.Basemap' which is not a subclass of 'esri.Basemap'
When attempting to step through the code, I noticed two Basemap.js files; one from my local project and one from the kitchen sink project. I'm wondering if this is the cause of the issue. I'm not sure how to tell the browser (or maybe it's Vite?) to load only the arcgis module from my local project.
When I npm install the layer selector package, I don't have the issue.
Making this change fixes the issue but causes other issues in the unit tests:
The text was updated successfully, but these errors were encountered:
When I use npm link to load the layer-selector into another local project on my machine, I get strange error messages in the console like this:
When attempting to step through the code, I noticed two
Basemap.js
files; one from my local project and one from the kitchen sink project. I'm wondering if this is the cause of the issue. I'm not sure how to tell the browser (or maybe it's Vite?) to load only the arcgis module from my local project.When I npm install the layer selector package, I don't have the issue.
Making this change fixes the issue but causes other issues in the unit tests:
The text was updated successfully, but these errors were encountered: