feat: add build-dir flag

[AlexanderKaran]

Moved my hacky version of detecting CoreJS into the CLI. Will only check build folder if you pass in a flag for now. Example output from testing a package from the framework tracker:

⏺ {
    "stats": {
      "name": "starter-next-js",
      "version": "0.1.0",
      "dependencyCount": {
        "production": 3,
        "development": 6
      },
      "extraStats": [
        {
          "name": "duplicateDependencyCount",
          "value": 12,
          "label": "Duplicate Dependency Count"
        },
        {
          "name": "vendoredPolyfillSize",
          "label": "Vendored Polyfill Size",
          "value": 112594
        }
      ],
      "installSize": 623096777
    },
    "messages": [
      {
        "severity": "suggestion",
        "score": 0,
        "message": "The package does not specify the \"type\" field. Node.js may attempt to detect the package type causing a small performance hit. Consider adding \"type\": \"commonjs\"."
      },
      ... (12 duplicate dependency warnings) ...
      {
        "severity": "warning",
        "score": 0,
        "message": "Vendored core-js 3.38.1 detected in .next/static/chunks/a6dad97d9634a72d.js (110.0 KB). This bundle includes 534 polyfills, of which 255 are unnecessary for modern browsers. Consider using a targeted polyfill
  strategy or removing core-js from your build."
      }
    ]
  }

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@e18e/cli@182

commit: 3120754

[dreyfus92]

awesome job @AlexanderKaran 😄 left a few comments

[dreyfus92]

this is creative but, it got me thinking since minified builds may strip comments containing these strings, should we add a note if we spot limitations?

[AlexanderKaran]

Yeah it was my hacky version I moved over lol

[AlexanderKaran]

I added a comment about them

[AlexanderKaran]

Messed around with the build outputs and added some more options

[dreyfus92]

cc. @43081j 👀

[dreyfus92]

Thank you Alex 😄