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
There is a JS bug which prevents loading of datatables on candidate pages. Looks to be possibly a Webpack error, but more investigation is needed to figure out the actual source of the problem. This is a bug produced after webapp+cms merge.
For reference, datatables on similarly styled pages like /data/elections/* to not seem be affected by this so it might be helpful to compare any differences in implementation and compilation of JS.
Might be helpful to look at: https://github.com/webpack/webpack/issues/959
The text was updated successfully, but these errors were encountered:
This might be a clue. The code is breaking at line 54. When adding a breakpoint there, I stepped through all the modules that are loaded. One particular moduleId: 111 is undefined. How can we traceback what module is being called here?
@johnnyporkchops Looks like there is a problem finding that particular module var maps = require('../modules/maps');. The pages in which this module is required is on the /fec/fec/static/js/pages/candidate-single.js, /fec/fec/static/js/pages/committee-single.js, and /fec/fec/static/js/pages/elections.js
There is a JS bug which prevents loading of datatables on candidate pages. Looks to be possibly a Webpack error, but more investigation is needed to figure out the actual source of the problem. This is a bug produced after webapp+cms merge.
For reference, datatables on similarly styled pages like /data/elections/* to not seem be affected by this so it might be helpful to compare any differences in implementation and compilation of JS.
Might be helpful to look at:
https://github.com/webpack/webpack/issues/959
The text was updated successfully, but these errors were encountered: