Does some part of VanJS make use of CommonJS module syntax?

[Ashvith10]

Like for example, this code snippet, I can't help but notice how it resembles CommonJS syntax:

const {a, div, p} = van.tags

[Tao-VanJS]

Not really. These are just standard JavaScript syntax for destructuring assignment.

[Ashvith10]

@Tao-VanJS sorry for not replying sooner, and thanks for answering. Usually, as we see in other framework libraries, we import components, right, but in this circumstance, we don't - why so?

[Tao-VanJS]

I don't quite understand the question. In

const {a, div, p} = van.tags

a, div, p are not components that need to be imported. They are just tag functions that can create native DOM elements.

[Ashvith10]

@Tao-VanJS I may be in the wrong here, but I was wondering - since we are importing "van", which includes a whole bunch of stuff including "tags", which in turn has a bunch of tag replacement for the HTML equivalent, wouldn't it be computationally expensive?

[Tao-VanJS]

No, van.tags is just a Proxy object which returns the same function with different bindings based on the property name:

van/src/van.js

Line 137 in e21df7d

tags: new Proxy(ns => new Proxy(tag, handler(ns)), handler()),