-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade us to use the latest versions of NodeJS and Babel #2304
Comments
Taking notes for myself: Going to node 18. Migrating from node-sass to sass. Upgrading gulp-sass to 5.1.0 fixes the problem without having to change node-sass. But npm install takes a lot longer. Installation with node-sass takes 2m 50s (has to compile it) Getting conflicting dependency warnings Running npm outdated:
rollup-plugin-babel-minify is deprecated in favor of rollup-plugin-terser
Need to migrate the gulpfile to use ESM https://gist.github.com/noraj/007a943dc781dc8dd3198a29205bae04 This means no more use of TypeError: Cannot read properties of undefined (reading 'filename') As a result, did not lazy load plugins anymore. chromium-dashboard/gulpfile.babel.js Line 92 in df8849c
Need to verify that this is no longer needed. Looks like I don't need it. With it, I get some circular dependency errors. sw-precache is using a vulnerable version of meow https://www.npmjs.com/package/sw-precache Turns out it was introduced here: bf8550d node_modules/got http2-push-manifest is not used anymore. can remove Remaining deprecation notices: npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated gulp-util is no longer used.
gulp-minify-html is no longer used rollup-plugin-lit-css is no longer used because the code now does styles the way mentioned in the docs: importing from .js files. The old way that used this plugin imported from css files. sw-toolbox is no longer used rollup-plugin-babel-minify uses babel-minify which is experimental. rollup-plugin-babel-minify recommends to use rollup-plugin-terser now but will wait until this PR: rollup/plugins#1323 Good stopping point.
Recommend getting rid of gulp by the way. a lot of the deprecation notices are due to gulp. Upon running all the commands in gulp, get this: Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($content-padding, 2) or calc($content-padding / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
╷
75 │ margin-bottom: $content-padding / 2;
│ ^^^^^^^^^^^^^^^^^^^^
╵
client-src/sass/blink.scss 75:18 root stylesheet
Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($content-padding, 2) or calc($content-padding / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
╷
84 │ margin-left: $content-padding / 2;
│ ^^^^^^^^^^^^^^^^^^^^
╵
client-src/sass/blink.scss 84:16 root stylesheet
Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($content-padding, 2) or calc($content-padding / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
╷
68 │ margin: $content-padding / 2 0;
│ ^^^^^^^^^^^^^^^^^^^^
╵
client-src/sass/forms.scss 68:13 root stylesheet Will not handle this. instead will create a bug for @jrobbins suggestion to phase out sass |
I'd also like to phase out our use of SASS, because we don't use much of it. We've already converted almost all of it to lit-css. |
Is your feature request related to a problem? Please describe.
Our current README.md says to use 12, whereas the current version is 16. This makes it more difficult for potential developers to set up a development environment.
Also, we have been declining PRs suggested by dependbot because they cause JS compilation errors. They depend on newer versions of Node, Babel, or other JS libraries. These PRs are often triggered by reported security vulnerabilities, so by declining them our app is left vulnerable.
Also, we don't seem to be able to use recent JS language features, for example the questionmark-dot operator.
Describe the solution you'd like
Get our app working on the latest version of Node, Babel, and do any needed JS library upgrades. Update README.md to tell potential developers that they can use the latest version of Node, or name a specific Node version that it current now.
The text was updated successfully, but these errors were encountered: