Remove unused dependencies

[SamChou19815]

Summary

A lot of dependencies are unused, they seem to be a left over of the old Vue CLI

• postcss related: Vue CLI enables them by default
• corejs: both gridsome and vue already declares them as dependencies
• eslint-import-resolver-webpack, eslint-config-airbnb-base: unused in the eslint config
• some babel stuff related to typescript support for vue: it should't be difficult to support ts in vue any more. New vue cli has good support for that. I was able to enable ts for course plan without much changes: https://github.com/cornell-dti/course-plan/pull/56/files
• eslint-plugin-import: already a dependency of vue's eslint plugins

Test Plan

• Linter can run.
• Website can be served locally.
• Website can be built.

[dti-github-bot]

[diff-counting] Significant lines: 33.

[ewlsh]

You removed the site's support for tsx/jsx which vue-cli does not support well out-of-box currently last time I checked.

Additionally, core-js was explicitly defined because some libraries would pull in v2 instead otherwise. That may no longer be the case.

[ewlsh]

You also removed our SVG loader?

[ewlsh]

I see CoursePlan's config did enable TSX support, I will have to look into this. When we upgraded TSX support was not functional out-of-box and required some tweaks and adjustments.

[dti-github-bot]

[deployment-bot] Deployed to https://5ecaf4c9d2193e07618e0411--cornelldti.netlify.app.

[SamChou19815]

I see CoursePlan's config did enable TSX support, I will have to look into this. When we upgraded TSX support was not functional out-of-box and required some tweaks and adjustments.

All the svgs still loads, which shows that it is not needed.

[ewlsh]

I see CoursePlan's config did enable TSX support, I will have to look into this. When we upgraded TSX support was not functional out-of-box and required some tweaks and adjustments.

All the svgs still loads, which shows that it is not needed.

No they don't. You're looking in the wrong place... the vue.config.js does not build the site. It builds the CMS preview content which in this build no longer supports SVGs.

https://5ecaeec2c94566a8f55a1d28--cornelldti.netlify.app/admin/#/collections/pages/entries/page-sponsor

[ewlsh]

We could unify our handling...

For the site we currently use: https://gridsome.org/plugins/gridsome-plugin-svg while for the CMS we use vue-svg-loader.

We could just use vue-svg-loader directly for the site too: https://gridsome.org/docs/assets-svg/#using-svgs-as-components

[ewlsh]

We could unify our handling...

For the site we currently use: https://gridsome.org/plugins/gridsome-plugin-svg while for the CMS we use vue-svg-loader.

We could just use vue-svg-loader directly for the site too: https://gridsome.org/docs/assets-svg/#using-svgs-as-components

gridsome-plugin-svg is just a wrapper around vue-svg-loader

[ewlsh]

@SamChou19815 changing the site's svg configuration can be punted to a separate PR if we choose to do it.