[Bug] ArcGIS layers not visible in deck.gl v9.1.4
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, typescript
- Domain
- data-visualization, frontend, web-dev
Research direction
Start by running examples/get-started/pure-js/arcgis with the package.json versions for deck.gl 9.1.4 and @arcgis/core 4.31.0, then compare it with the working 9.0.38 CodeSandbox. Investigate the ArcGIS integration and rendering behavior without assuming the build tool is responsible. Done means the layers are visible and the ArcGIS base map matches the expected rendering.
Written by the indexing model from the issue text.
Description
Description
When using deck.gl v9.1.4, layers do not render on an ArcGIS map. The base map also appears incorrect.
I have built two CodeSandbox examples, both based on the "Get Started / Pure JS / ArcGIS" example from deck.gl's GitHub repository:
🔗 Reference Example: deck.gl/examples/get-started/pure-js/arcgis
Working version (v9.0.38)
✅ This sandbox works as expected, with visible layers and correct base map:
🔗 Working Example (v9.0.38)
Broken version (v9.1.4)
❌ This sandbox does not display layers, and the base map is incorrect:
🔗 Broken Example (v9.1.4)
We observe the same issue in our production application, which uses Next.js (not Vite), so the problem does not seem related to the build tool.
Note: there are no errors in the browser's console.
Flavors
- Script tag
- React
- Python/Jupyter notebook
- MapboxOverlay
- GoogleMapsOverlay
- CARTO
- ArcGIS
Expected Behavior
- The layers added to the ArcGIS map should be visible.
- The base map should display correctly, as it does in v9.0.38.
- Upgrading from deck.gl v9.0.38 to v9.1.4 should not break rendering.
Steps to Reproduce
- Clone the official deck.gl v9.1.4 ArcGIS example:
git clone --branch v9.1.4 https://github.com/visgl/deck.gl.git
cd deck.gl/examples/get-started/pure-js/arcgis
- Update the
package.jsonto specify the exact versions:
Open the package.json file and modify the dependencies and devDependencies as follows:
{
"name": "deckgl-example-pure-js-esri-arcgis",
"version": "0.0.0",
"private": true,
"license": "MIT",
"scripts": {
"start": "vite --open",
"start-local": "vite --config ../../../vite.config.local.mjs",
"build": "vite build"
},
"dependencies": {
"@arcgis/core": "4.31.0",
"@deck.gl/arcgis": "9.1.4",
"@deck.gl/core": "9.1.4",
"@deck.gl/layers": "9.1.4"
},
"devDependencies": {
"vite": "^4.0.0"
}
}
- Install the dependencies:
npm install
- Start the development server:
npm start
- Observe the issue:
- No layers appear on the ArcGIS map.
- The base map appears incorrect.
- If you downgrade to deck.gl v9.0.38, the issue disappears.
🛠️ Alternatively, you can reproduce the issue using the provided CodeSandbox examples linked earlier.
Environment
- Framework version: deck.gl@9.1.4
- Browser: 133.0.6943.127
- OS: MacOS 15.3.1
Logs
No errors logs, but layers do not render
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from visgl/deck.gl
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·