32
Are we ready for javascript without a build step on the front end in 2023? (lemmy.fbmac.net)
submitted 3 years ago by to c/programming@programming.dev
48 comments fedilink hide all child comments
 

On the current typescript / anti-typescript internet drama I saw someone mention javascript without a build step.

Do you think we're already there?

Last time I attempted it:

  • there were too many libraries I couldn't import
  • JSX (using babel) had a warning saying you shouldn't do it in the browser for production
  • there was some advice against not using a bundler, because several requests for different .js files is slower and bigger than a bundled package
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 3 years ago (1 child)

Isn't Babel part of the build step? I might not be misunderstanding with what you mean by build step here.

In general, you probably can't avoid a bundler for the browser without significant compromises on performance and developer experience.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 3 years ago

    I'm asking mostly out of curiosity, but I had a use case that I would like to completely avoid a build step. At work we have a very old web interface, that when I attempt to sell the idea of any major improvement the answer is "this is end of life, we are rewriting it". But the rewrite will take a long time, and it is easier to make gradual improvements without introducing new tooling. This one is from the 90s, there the JS is in a folder and is shipped as is.

  • permalink
  • fedilink
  • source
  • parent