Before installing sprockets-commoner, I would get no errors. Now, these variables are undefined. The variables are still present at the bottom of application.js (after compilation, in the browser).
It makes me very cautious to move across, because I don't know what other things will break. The application is quite large and has been written over a long time.
Any advice as to how to rectify this (or even what is causing it? I can't see anything that Commoner has added that would cause this).
Hey,
I'm trying to get a legacy project onto ES, and I'm having a few issues.
I'm only targeting
*.es6.js
files, so that we can slowly move across over time. That seems to be working fine forapplication.js
.My problem is that there are some variables defined at the bottom of
application.js
, and in other files at the top level.They are then accessed from the templates.
e.g.
then, in the page's template
Before installing sprockets-commoner, I would get no errors. Now, these variables are undefined. The variables are still present at the bottom of application.js (after compilation, in the browser).
It makes me very cautious to move across, because I don't know what other things will break. The application is quite large and has been written over a long time.
Any advice as to how to rectify this (or even what is causing it? I can't see anything that Commoner has added that would cause this).