The dash-daq package is in quite an unfortunate situation. Starting with Dash 4 (maybe dash 3 as well, didn’t confirm), dash-daq needs at minimum the latest version: 0.6.0. Version 0.5.0 is not compatible. Looking at pypi, the latest version available is 0.6.0. However, on npm (and by extension unpkg), the latest version is 0.5.0.
This causes issues for Dash apps using dash-daq that are deployed on a cloud server. On dashboard load it tries to load the dash-daq bundle from unpkg, but it can’t for version 0.6.0 since it is not available. On the other hand, Dash 4 doesn’t work with version 0.5.0. That means that apps using dash-daq are stuck and cannot follow the latest Dash updates anymore.
Note that running a dash app locally is all fine and dash-daq 0.6.0 loads just fine in that situation.
I made a GitHub issue on the topic, but the repo doesn’t seem to be tracked much lately. So I want to draw some attention to the issue here on the forum. What does it take to create a dash-daq js bundle and publish the latest version on npm?
In the deployed environment, make sure the correct version is pinned.
To force use of the version included in the Python bundle, set app = Dash(serve_locally=True).
You could open an issue in Dash to ask about the npm deployment of the latest release. It appears that step may have been missed in the last Dash DAQ release.
Dash DAQ is not actively maintained. Have you considered migrating to other components?
The correct version is pinned, I confirmed that with the version that is being asked by the browser.
I have serve_locally=False for my cloud deployments. It’s a setting from a long time ago when it was necessary to have it that way. Didn’t change it afterwards. I could try to see if any errors pop up if I flip it again.
I’ll open an issue in the main dash repo referring to the dash daq issue. I saw that it was not really maintained, however with the release last year and the presence of the library in the dash documentation I thought it was at least monitored. Not sure where they keep the latest version of dash-daq, internally or on that Github repo. The repo is not yet archived.
The problem arose with one of my older tools, where I regularly update the framework around the tool, but keep the content untouched, or only do minimal changes. For this particular dashboard, moving away from dash daq is more effort then I could justify. So I only want to do it if it is absolutely necessary.
