|
BLOG
|
Hello @KeyHunter, thanks for the detailed writeup, that nesting clue is exactly the right thread to pull. The "is duplicated" message comes from the build scanning your-extensions\widgets and finding the same manifest name registered twice, so somewhere there are two copies. A single correctly placed copy can't trip it, which is why a fresh basemap-gallery-custom on its own doesn't fix it: the second copy is still sitting elsewhere. Three places to check, in order: a nested folder at widgets\basemap-gallery-custom\basemap-gallery-custom (the manifest has to be one level up, directly inside basemap-gallery-custom); any leftover folder from your 1.19 build, including an old basemapToggleCustom folder this widget was renamed from; and a stale compiled copy in client\dist\widgets carried over from 1.19. For that last one, stop the client, delete the matching folder under dist\widgets, then npm start again. Your "remove it and nothing shows in the Entrypoint list" symptom is the tell that the copy you kept is nested too deep. I also just standardized this widget and put it on this blog post and GitHub with a README that walks through install placement and this exact error: https://github.com/brianmcleer/basemap-gallery-custom-widget. Grab the v1.0.0 release, drop the folder in so the manifest sits directly inside basemap-gallery-custom, and you should be set. Let me know how it goes.
... View more
2 weeks ago
|
0
|
0
|
60
|
|
DOC
|
06/03/2026: Added package.json so jsPDF installs automatically with the standard "npm install" in the EB client folder. No separate jsPDF install needed.
... View more
2 weeks ago
|
0
|
0
|
1190
|
|
BLOG
|
Thanks @SunshineLuke90 . I went ahead and added a package.json and package-lock.json to the widget following your approach, so the dependencies now install automatically when you run the standard npm install in the client folder. No more manual npm install commands needed. I also included the exb-widget keyword and an Apache 2.0 license to line up with the conventions you laid out in your Standardizing Custom Widget Sharing thread. Really appreciate you walking through this, it makes the widget a lot easier for others to pick up and use, and I think the standardization effort is a great direction for the community. I am going to go through all of my widgets and standardize more using this approach.
... View more
2 weeks ago
|
0
|
0
|
425
|
|
BLOG
|
6/03/26: Enhancements (1.20 version only) Add support to launch and open Mailing Labels or Property Report when they are nested in accordion widget (Thank you @KeyHunter for idea and testing) Standardized package structure: added package.json, README.md, LICENSE (Apache 2.0), .gitignore, and .npmignore so dependencies install automatically with the standard `npm install` in the client folder. No per-dependency install commands needed.
... View more
2 weeks ago
|
1
|
0
|
568
|
|
BLOG
|
Thank you @KeyHunter, I think your question still needs research and further discussion. From our private messages earlier this week I'm glad you were able to get the dependencies resolved.
... View more
3 weeks ago
|
0
|
0
|
580
|
|
BLOG
|
@Bertrand_Laurancin thank you for your solution and compliments @KARIMLABIDI glad that you could get it worked out!
... View more
3 weeks ago
|
1
|
0
|
770
|
|
BLOG
|
Thank you @KARIMLABIDI , at this point I would recommend posting in the custom widgets link I posted above. I would also normally suggest a support case, but I don't think they will be able to do much with custom widgets involved.
... View more
3 weeks ago
|
0
|
0
|
865
|
|
BLOG
|
@KARIMLABIDI if that does not work, I think because you are getting the error on multiple widgets and it does not seem to be constrained just to right click, your question may get more exposure if you post it to the questions section of the Group Experience Builder Custom Widgets https://community.esri.com/t5/experience-builder-custom-widgets/bd-p/eb-custom-widgetsforum-board
... View more
3 weeks ago
|
0
|
0
|
880
|
|
BLOG
|
@KARIMLABIDI after looking at your error more, I strongly think that you are running into a folder path limit, especially since you are using OneDrive. If you are able to deploy EB 1.20 right to your C Drive it may resolve the issue. The errors to me point to a directory issue, and I used to store my EB DE on a deeper folder structure and had similar issues.
... View more
3 weeks ago
|
0
|
0
|
887
|
|
BLOG
|
Thank you @KARIMLABIDI , without being able to replicate the issue or see your system fully (not that I am suggesting that), it is hard to troubleshoot and come up with a solution. This widget does not require any npm dependencies beyond what is OOTB of EB, so that should not be a culprit. I am purely speculating on troubleshooting steps below, but might be worth a try. - Fresh install of 1.20 and put downloaded widgets in ...arcgis-experience-builder-1.20\client\your-extensions\widgets - Sometimes I have issues with long file paths, so I put my EB DE right on the C drive, that might worth trying so your set up is C:\arcgis-experience-builder-1.20 - If you have not already, try using the suggested version of Node.js for EB DE 1.20
... View more
3 weeks ago
|
0
|
0
|
931
|
|
BLOG
|
@KARIMLABIDI can you try the below steps if you feel okay doing so? Close any running EB processes. Delete C:\Users\LABIDI\node_modules entirely. While you're there, delete C:\Users\LABIDI\package.json and C:\Users\LABIDI\package-lock.json if those exist. In your EB folder, delete your-extensions/node_modules/.cache to clear stale resolution. Re-run npm run build:for-download.
... View more
3 weeks ago
|
0
|
0
|
978
|
|
BLOG
|
@KARIMLABIDI I think I found the bug in config.json. I updated the 1.20 zip on this blog post. Please let me know if you are still getting the error after you get the latest 1.20 zip from here and confirming you are using the latest mailing labels widget.
... View more
4 weeks ago
|
0
|
0
|
1039
|
|
BLOG
|
@KARIMLABIDI did you also update the mailing labels widget if you are using that?
... View more
4 weeks ago
|
0
|
0
|
1041
|
|
BLOG
|
Hello @KARIMLABIDI, one difference between my environment and yours is the version of Node.js. I am currently on 24.15.0. and it looks like you are using 26.2.0. The recommended version for Experience Builder Developer Edition 1.20 is Node.js 24. This may not be the reason you are getting the errors, but is a system difference between my setup vs yours. https://developers.arcgis.com/experience-builder/guide/release-versions/
... View more
a month ago
|
0
|
0
|
1049
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | yesterday | |
| 2 | Wednesday | |
| 1 | Tuesday | |
| 2 | Friday | |
| 5 | a week ago |
| Online Status |
Online
|
| Date Last Visited |
yesterday
|