Programming

17668 readers

179 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

Are we ready for javascript without a build step on the front end in 2023? (lemmy.fbmac.net)

submitted 1 year ago by [email protected] to c/programming

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

[–] JackbyDev 0 points 1 year ago (1 children)

I don't do front end work so I don't know how all the terms are used. If by build step you mean any sort of CI process then I would say no, I think automated tests are important and should be ran before pushing.

If you just mean some sort of transformation, transpilation, bundling, etc. then I don't know enough to answer. My gut feeling is that the question is framed incorrectly. Many of these things were made as workarounds for various problems (or to make things easier). If you don't have those problems then you don't need those solutions. It doesn't have anything to do with progress (as in what year it is). Originally JavaScript was just plain old JavaScript. If it worked then it can work now. If you need the solutions people have made to get around limitations and short comings and vanilla JavaScript can't do it then you'll still need those solutions.

[–] alr 1 points 1 year ago

That's a great point. In any sort of enterprise system, you should be unit-testing your front end when you commit, and you should be UI-testing your front end before you deploy. If you're in a CI/CD pipeline, that normally happens right after the build step. If you need to have the pipeline running anyways, you might as well build.