[revisit sass] Feat/px2vw adopt nuxt.js with SASS math.div() working

[mcdmaster]

👏 解決する issue / Resolved Issues

• close [Issue] SASS BUILD ERROR! (sass) resume update sass, sass-loader, eslint etc. #6946
• close SASS / SCSS の割り算の記法 #6346
• [Bug Report][2.5.0] New Sass Deprecation Recommended vuetifyjs/vuetify#13694

📝 関連する issue / Related Issues

• Feat/pw2vw #6452
• Update dependency sass to v1.42.1 #6420
• sassのバージョンを1.32.12に（暫定的処置） #6417
• [Draft] apply SASS division #6380
• fix(sass) add "hoistUseStatements: true" option to ensure '@use sass:math' works vuetifyjs/vuetify#14326
• fix(styles): revisit sass restriction remediation vuetifyjs/vuetify#13938
• fix(styles): deal with new sass restriction vuetifyjs/vuetify#13704[
• fix: avoid crash of a template-based procedure nuxt-modules/i18n#1381

⛏ 変更内容 / Details of Changes

Every build time, our build tool looks like as if it deep-dives into the lowest level of enterire directories with our own or other open-source libraries / included items. In that case, we have been having some difficties like:

• Firstly, in terms of "Changes" technically done, they are performed as workarounds and/or remediations to have our Nuxt.js instance (PROD assumed, naturally) keep itself up and running; they have been usually backed by testing excel accompanied with our Linting strategy
• The bunches in tons ot error dumps, which SASS itself produces and throws them nudging the developer(s) to arise and start working on applying the change toward the use of SASS math.div() ffacility with advantage as early as he/she can;
• Too much GBs of its log outputs are apparently threaten the developer's system resource, because they can easily terminate his/her good hacking activities with the network unexpedly occupied
• Although it is figured out already that the most used and mass-volume application component Vuetify package has the greatest number of old SASS files, which produces tons of logs to exclaim that our system is 'deprecated' behind the latest SASS releases (here we can see that Vuetify is being outdated because of potential reluctancy of their changing mind)
• At this time, SASS, sass-loader, Eslint etc are configured (as default) NOT TO be updated automatically; contrarily, this PR does NEVER cope with any kind of "downgrade" approach - just fix & go.
• Hence I tried hard to suppress SASS message outputs on my end: I suppose this is almost completed but still requires sophistication and easy maintenability because it should not spend our hours to supplying Oxygen to old running Vuetify@2.

📸 スクリーンショット / Screenshots

[kaizumaki]

@mcdmaster すみません、こちらnetlifyのdeploy previewが動いていないので、ビルドスクリプトが根本的に正常に機能していないものと思われますが、いかがでしょう。

[mcdmaster]

@kaizumaki ご心配とご迷惑を掛けております。

為念お伝えすると、「ビルドスクリプトが根本的に正常に機能していない」というほどのクリティカルなものではありません。
Lint 絡みで条件判定や、recommended テンプレをはじめとするルールに載らないコードを直していたら意外に時間が掛かってしまっています。
そのため、今の段階でもなお Ongoing 状態を招いているというのが正解です。

可能な限り早めの事態収拾を図りますので、もうしばらくお待ちいただけますか

[mcdmaster]

こちら、なんだかどうにもラチが開かないので、いったんクローズしますね。
当初の目的は、単純に scss の文中で math.div() 関数を動かせるようにしたいだけだったんです。
しかしながら、聞き分けのない Vuetify チームともめてみたりとか、まあ、貴重な経験ではあったんですけど、正直疲れました。
Vue3 の適用を急ぐ方がむしろスムーズかもしれません