Something I recently figured:
Ruby-on-Rails does require something called webpacker, which again does require node-sass, currently version 4.14.
That one depends on node, and is provided as a precompiled binary, respective of the node version. For FreeBSD, node-14 is not supported, only node-12 and 13. Node-13 is not available on FreeBSD, and node-12 depends on python 2.7.
If there is no binary available, node-sass will automatically build locally (lengthening the deploy time) - supported or not. For this it requires node-gyp, in the version 3.8, and this again requires python 2.7.
There are newer node-gyp probably not requiring python-2, and there is a node-sass 5.0 that does use these (node-14 and 15 also not supported on FreeBSD). Now lets see how long it will take until the whole daisy-chain will establish that. I might suppose, longer than december, because we already have december.
If this may finally come to some kind of fruition, when are people expected to do the testing of their applications with new software versions? At christmas?
(I'm not worried, but I admit I was expecting quite this since the bold idea of dumping python 2.7 came up. And I suppose, some people will notice the issue only when they fail to reinstall python2.7, and then in turn fail to deploy - or vice versa - as the whole thing is nicely hidden in automagical stuff. Nevertheless, since november, some people seem to actually recognize there might be an issue: https://github.com/rails/webpacker/pull/2716#issuecomment-722062481)
Ruby-on-Rails does require something called webpacker, which again does require node-sass, currently version 4.14.
That one depends on node, and is provided as a precompiled binary, respective of the node version. For FreeBSD, node-14 is not supported, only node-12 and 13. Node-13 is not available on FreeBSD, and node-12 depends on python 2.7.
If there is no binary available, node-sass will automatically build locally (lengthening the deploy time) - supported or not. For this it requires node-gyp, in the version 3.8, and this again requires python 2.7.
There are newer node-gyp probably not requiring python-2, and there is a node-sass 5.0 that does use these (node-14 and 15 also not supported on FreeBSD). Now lets see how long it will take until the whole daisy-chain will establish that. I might suppose, longer than december, because we already have december.
If this may finally come to some kind of fruition, when are people expected to do the testing of their applications with new software versions? At christmas?
(I'm not worried, but I admit I was expecting quite this since the bold idea of dumping python 2.7 came up. And I suppose, some people will notice the issue only when they fail to reinstall python2.7, and then in turn fail to deploy - or vice versa - as the whole thing is nicely hidden in automagical stuff. Nevertheless, since november, some people seem to actually recognize there might be an issue: https://github.com/rails/webpacker/pull/2716#issuecomment-722062481)
