document.currentScript | Polyfill for HTML5 's document.currentScript | Form library

You can't play a video automatically with sound. There's a thing called "Autoplay Policy", at least for Chrome, but all other browsers are trying to block it.

See more information here.

Yes and no.

• When the script in-question is a JS module in its own .js file that's directly loaded into a

According to the HTML Spec on the Source Element,

Dynamically modifying a source element and its attribute when the element is already inserted in a video or audio element will have no effect. To change what is playing, just use the src attribute on the media element directly, possibly making use of the canPlayType() method to pick from amongst available resources. Generally, manipulating source elements manually after the document has been parsed is an unnecessarily complicated approach.

Therefore, no matter what you do to the source element, you can't change the video unless the new src is applied directly to the video element.

Replacing the source element also has no effect on the video that plays. The source element's src attribute may changed but the video will keep on playing.

Therefore, you should leave your source's src attribute empty until the JavaScript code sets it or

Leave out the source tag all together and apply the src straight to the video.

Math.floor(Math.random() * 7 + 1); is exactly the same thing as Math.ceil(Math.random() * 7);

Tl;dr Schedule a microtask

The point being that using await schedules the rest of the function as a microtask.

Please note that this answer don't attempt in any way to detect whether a value has been discarded or not. This is solely in answer to the first paragraph (Use-case), dropping the need for the both static code analysis and run-time source code parsing.

The purpose is just to yield control to the calling routine.

await nonPromiseValue is the same as await Promise.resolve(nonPromiseValue). It completes "instantly" but still schedules the code after the await expression to run later. So with f = async () => { await 1; 2;} and calling f(); g() the code will first reach await 1 -> sleep f and schedule the rest on the microtask queue -> call g() -> (eventually when the microtask queue gets to it) resume f() continuing with 2

The values from which to what it changes, or whether it does at all, do not make difference.

I'd move the sources into an array and dynamically set the source of the video from one of the items in the array using javascript.

You need to use Math.random to choose a random video from a list. Then the video source to that chosen video, and play it.

The problem here was in external-component.js

It seems that the name variable should match the name of the actual file passed from the server

This can't just match the name string passed in to the File(bytes, file, "name") call, but the actual file name in the file system (excluding the .vue extension)

After setting that value properly it's working fine

I managed to overcome these errors by updating my controller endpoint to:

When you import any module (either using import or

...will log I was imported only once.

From that, we can clearly see that a module may be imported multiple ways at the same time, so there can not be any way to determine the way how a module was imported...

...as long as you don't use exports.

Including a module using a script tag is identical to the import 'modulepath' syntax, that is, in MDN's words, importing a module for its side effects only.

That means, that no exports are taken, the module is just evaluated.

However, if one of the exports is used (called, for example) you can rule out the possibility that the module's instance that used the export was imported by a script tag.

The following scenario is still possible, though: