Right now, we use a htmldep to inject a window.shinyreact JS object. This is done to keep the R/Python packages forced to be in-sync with the JS files.
Ideally, we don't have a forced global dep and instead its available via NPM. However, my current understanding is that we can not couple the JS installed via the build and the API that the python is expecting. We could add a runtime assert, but still feels brittle.
Vendor-ing the JS files also runs the issue that the JS is stale compared a the newly updated python package.
Is there a better approach? Is there a way that npm can install from python assets?
If achieved, we can drop the global declaration of window.shinyreact. 🎉
This would require everyone to build their JS, but that's expected for the ui.tsx approach.
Right now, we use a htmldep to inject a
window.shinyreactJS object. This is done to keep the R/Python packages forced to be in-sync with the JS files.Ideally, we don't have a forced global dep and instead its available via NPM. However, my current understanding is that we can not couple the JS installed via the build and the API that the python is expecting. We could add a runtime assert, but still feels brittle.
Vendor-ing the JS files also runs the issue that the JS is stale compared a the newly updated python package.
Is there a better approach? Is there a way that npm can install from python assets?
If achieved, we can drop the global declaration of
window.shinyreact. 🎉This would require everyone to build their JS, but that's expected for the ui.tsx approach.