Can we talk about "reproducible builds" when working with interpreted languages?

This is a vocabulary question. I know the concept of reproducible build as the guarantee we can build software from the sources on a different host or at a different time, but producing an end-product identical at the byte level each time.

But I'm not quite sure if we can talk about (or if there is an equivalent to) "reproducible builds" when working with interpreted languages (PHP, JavaScript, Python, ...)

Should I talk about "reproducible build" when it is just a matter of providing a well-controlled environment1?

1 throuh a virtual environement, a container, a VM or whatever elese

A "build" does not have though to be a compilation step.

".. the term build is similar to that of any other field. That is, the construction of something that has an observable and tangible result."
https://en.wikipedia.org/wiki/Software_build

More important in this context is to be able to reuse results of your build in other contexts to build new things.

That is, also in PHP and Javascript you could produce some packaged artefacts, be it a zip file or language specific archive linkable to a dependency manager: NPM in Javascript and Composer in PHP for example.

StackExchange DevOps Q#6338, answer score: 2