A WeakSet only stores objects, and its elements are garbage collected when there is no other reference to them. WeakSets are useful for holding "weak" references to objects, meaning they won't prevent an object from being garbage collected.

The WeakSet does not have a 'clear' method, which is available in a regular Set. The 'clear' method in a Set is used to remove all elements from the Set, but WeakSet lacks this functionality.

Yes, you can use both named and default exports in the same ES6 module. This allows you to export a single "default" value along with multiple named exports from the same module.

Yes, an arrow function has its own this context, which means it does not bind its own this but retains the this value of the enclosing lexical scope. This behavior can be advantageous in certain scenarios.

By setting "type": "module" in package.json, Node.js is informed to treat JavaScript files as ES modules, allowing the use of import/export syntax and adhering to ES6 module behavior.

Arrow functions in ES6 use a shorter syntax (=>) compared to the traditional function declaration. This concise syntax is especially useful for simple one-liner functions.

In ES6, the extends keyword is used to inherit properties and methods from another class.

Dynamic imports in JavaScript have a positive impact on code splitting by allowing modules to be loaded on-demand. This enhances modularity, as only the necessary code is fetched when needed, reducing the initial load time of the application.

Pure functions should not have side effects, and modifying global state is considered a side effect. Therefore, they should not modify any global state.

Arrow functions capture the this value from their surrounding lexical scope. In the context of higher-order functions, this is crucial to understanding and avoiding potential issues.