You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reconsider the decision to be able to execute ES6 content inside *.js files. It seems that there is a difference in the eval of the content:
*.js files are evaluated each time.
*.mjs files are evaluated only once.
Also there is a difference between the semantics of the two file types.
This doesn't lead to a difference in the performance (e.g. faster execution time, memory consumption, etc.), but could lead to a difference in the behaviour (e.g. content being cached inside *.mjs files).
Impacted areas:
TypeScript compilation - should result into *.mjs files instead of *.js files
This discussion was converted from issue #3407 on February 08, 2024 14:27.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Reconsider the decision to be able to execute ES6 content inside
*.js
files. It seems that there is a difference in the eval of the content:*.js
files are evaluated each time.*.mjs
files are evaluated only once.This doesn't lead to a difference in the performance (e.g. faster execution time, memory consumption, etc.), but could lead to a difference in the behaviour (e.g. content being cached inside
*.mjs
files).Impacted areas:
*.mjs
files instead of*.js
filesBeta Was this translation helpful? Give feedback.
All reactions