Skip to content

Why is webpack processing the .tsbuildinfo files? #11

@chancancode

Description

@chancancode
~/C/ember-debug ❯❯❯ yarn build
yarn run v1.22.4
$ yarn build:webpack
$ webpack -p
Hash: 760f366086dcd1d35a3b
Version: webpack 4.43.0
Time: 6079ms
Built at: 11/02/2020 6:58:53 PM
                                             Asset       Size  Chunks                    Chunk Names
    ../packages/ember-debug-global/dist/index.d.ts   46 bytes          [emitted]
../packages/ember-debug-global/dist/index.d.ts.map  104 bytes          [emitted]
      ../packages/ember-debug-global/dist/index.js  908 bytes          [emitted]
  ../packages/ember-debug-global/dist/index.js.map  864 bytes          [emitted]
   ../packages/ember-debug-global/tmp/.tsbuildinfo    292 KiB          [emitted]  [big]
           ../packages/ember-debug/dist/index.d.ts  323 bytes          [emitted]
       ../packages/ember-debug/dist/index.d.ts.map  371 bytes          [emitted]
             ../packages/ember-debug/dist/index.js  417 bytes          [emitted]
         ../packages/ember-debug/dist/index.js.map  505 bytes          [emitted]
          ../packages/ember-debug/tmp/.tsbuildinfo    291 KiB          [emitted]  [big]
                                    bookmarklet.js   12.2 KiB       0  [emitted]         main
                                        index.html   1.02 KiB          [emitted]
Entrypoint main = bookmarklet.js
[2] ./bookmarklet.ts 72 bytes {0} [built]
[3] ./packages/ember-debug-global/dist/index.js + 1 modules 1.59 KiB {0} [built]
    | ./packages/ember-debug-global/dist/index.js 775 bytes [built]
    | ./packages/ember-debug/dist/index.js 847 bytes [built]
    + 2 hidden modules

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  ../packages/ember-debug/tmp/.tsbuildinfo (291 KiB)
  ../packages/ember-debug-global/tmp/.tsbuildinfo (292 KiB)

WARNING in webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/
Child HtmlWebpackCompiler:
     1 asset
    Entrypoint HtmlWebpackPlugin_0 = __child-HtmlWebpackPlugin_0
    [0] ./node_modules/html-webpack-plugin/lib/loader.js!./index.html 1.38 KiB {0} [built]
✨  Done in 8.00s.

Not sure if this has always been the case or it was something we did "recently". Webpack is complaining that some of the "asset" files are too big, and it turns out it was talking about the .tsbuildinfo files. These are basically internal caches used by TypeScript, and I'm not sure why Webpack would need to process them at all. I think something is probably misconfigured somewhere, or maybe the warning is just wrong/superfluous... needs investigation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions