How to reduce the size of commons.js in Next 8?

[wq93]

How to reduce the size of commons.js?
next.js version: 8.0.3

Size: 185K

[olpeh]

Show your dependencies in you package.json, it might give a hint for what you could possibly leave out.

[wq93]

"dependencies": {
    "@next/bundle-analyzer": "^9.0.3",
    "@zeit/next-css": "^1.0.1",
    "axios": "^0.18.0",
    "axios-extensions": "^3.0.5",
    "braft-editor": "^2.3.8",
    "classnames": "^2.2.6",
    "cookie-parser": "^1.4.4",
    "express": "^4.16.4",
    "filepond": "^4.7.4",
    "filepond-plugin-file-validate-size": "^2.2.0",
    "filepond-plugin-file-validate-type": "^1.2.4",
    "filepond-plugin-image-exif-orientation": "^1.0.6",
    "filepond-plugin-image-preview": "^4.5.0",
    "html-react-parser": "^0.10.0",
    "http-proxy-middleware": "^0.19.1",
    "js-cookie": "^2.2.0",
    "lodash": "4.17.14",
    "lru-cache": "^5.1.1",
    "mobile-detect": "^1.4.3",
    "mustache": "^3.1.0",
    "next": "^8.0.3",
    "next-cookies": "^1.1.2",
    "next-redux-wrapper": "^3.0.0-alpha.2",
    "next-seo": "^3.0.0",
    "normalize.css": "^8.0.1",
    "nprogress": "^0.2.0",
    "photoswipe": "4.1.1",
    "prop-types": "^15.7.2",
    "react": "^16.8.4",
    "react-dom": "^16.8.4",
    "react-filepond": "^7.0.1",
    "react-ga": "^2.5.7",
    "react-paginate": "^6.3.0",
    "react-rating": "^2.0.0",
    "react-redux": "^5.1.1",
    "react-transition-group": "^2.9.0",
    "redux": "^4.0.1",
    "redux-actions": "^2.6.4",
    "redux-thunk": "^2.3.0",
    "styled-components": "^4.1.3",
    "swiper": "^4.5.0",
    "winston": "^3.2.1",
    "winston-daily-rotate-file": "^4.3.0"
 },

[Timer]

Upgrading to Next.js 9.3+ may help a lot in this regard.

[wq93]

Is there another way?

[Timer]

Not really. Next 8 was not designed to allow you to load the minimal set of dependencies for an individual page route—it was heuristic based. Next 9.3+ solves this issue.

You could defer all package usage to next/dynamic, but this may not satisfy your application's requirements.

[Timer]

Note, upgrading from Next 8 to 9 should not entail any breaking changes. It should be as easy as npm i next@latest.