4 ms·

Surely this is not shaving from the build? It's shaving from the source. The build would never have 80MB of TypeScript types included.

Karellen 4y ago
The article is clearly talking about the build process, which was reading 80MB of TypeScript sources. You seem to be confusing that with the build output, aka object code or target.
- returningfory2 4y ago
  Not the parent, but my interpretation of "my Typescript build" would be the build output, not the input to the build process.
  - OJFord 4y ago
    'Build' is commonly used both ways, and not just in software.
  - Karellen 4y ago
    But the article is very clear about what it means by "build". The three places that it uses the term wrt software, in context, are: > would you rather have TypeScript build your code 20% faster? > did this make my build faster? > You might be surprised what's making it into your build! which are clearly talking about the build process and inputs, not its output.
    - afavour 4y ago
      I think my confusion was the use of MB. If the headline had been "I shaved 200ms from my build" it would be very clear it was about the build process. But when I see MB I immediately think about output.
  - tshaddox 4y ago
    That interpretation doesn’t even make sense in TypeScript though, does it? You don’t build a “TypeScript app bundle” and send it off to be installed on your TypeScript executor. The only interpretations I can think of for “TypeScript build” would be 1) the typechecking process, which just outputs a list of type errors and warnings or 2) the transpilation process which strips out all the TypeScript syntax from your code leaving you with valid JavaScript.
geewee 4y ago
Yes, the title is just misleading and a little clickbaity
mstudio 4y ago
This was my question as well. The article does answer the question, but off the bat I'd assumed the author was talking about output/dist. The web treemap cli is a great tip. If you are using webpack, webpack-bundle-analyzer is a helpful tool for quickly finding bloated packages. It's definitely helped me cut down my build times: https://github.com/webpack-contrib/webpack-bundle-analyzer https://github.com/webpack-contrib/webpack-bundle-analyzer

Karellen 4y ago

The article is clearly talking about the build process, which was reading 80MB of TypeScript sources. You seem to be confusing that with the build output, aka object code or target.

returningfory2 4y ago
Not the parent, but my interpretation of "my Typescript build" would be the build output, not the input to the build process.
- OJFord 4y ago
  'Build' is commonly used both ways, and not just in software.
- Karellen 4y ago
  But the article is very clear about what it means by "build". The three places that it uses the term wrt software, in context, are: > would you rather have TypeScript build your code 20% faster? > did this make my build faster? > You might be surprised what's making it into your build! which are clearly talking about the build process and inputs, not its output.
  - afavour 4y ago
    I think my confusion was the use of MB. If the headline had been "I shaved 200ms from my build" it would be very clear it was about the build process. But when I see MB I immediately think about output.
- tshaddox 4y ago
  That interpretation doesn’t even make sense in TypeScript though, does it? You don’t build a “TypeScript app bundle” and send it off to be installed on your TypeScript executor. The only interpretations I can think of for “TypeScript build” would be 1) the typechecking process, which just outputs a list of type errors and warnings or 2) the transpilation process which strips out all the TypeScript syntax from your code leaving you with valid JavaScript.

geewee 4y ago

Yes, the title is just misleading and a little clickbaity

mstudio 4y ago

This was my question as well. The article does answer the question, but off the bat I'd assumed the author was talking about output/dist. The web treemap cli is a great tip. If you are using webpack, webpack-bundle-analyzer is a helpful tool for quickly finding bloated packages. It's definitely helped me cut down my build times: https://github.com/webpack-contrib/webpack-bundle-analyzer https://github.com/webpack-contrib/webpack-bundle-analyzer