Replies: 3 comments
|
@vmutafov converted to discussion, to expose the topic and also receive feedback from the community. |
0 replies
|
If possible, I think it would be great to support both and to differentiate between them, based on the file extension, either |
0 replies
|
A reference from V8 documentation on why If we can "solve" with it also the irritating issue for unrecognisable client-side and server-side script files in a single project, will be very beneficial long-term as well. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We should decide if Dirigible users would be allowed to mix CommonJS and ES6 modules. Although it seems great at a first glance to support both specifications in a single project, there may be complications while implementing this.
If it is not hard for implementing, it would be good to support both specifications as it would allow users to easily migrate their applications to the ES6 modules syntax. We can see how NodeJS approached this and if they support both specifications to be used in a single project. Maybe we can differentiate the two specs by the file extension -
.jsfor CommonJS and.mjsfor ES6 moduled JS files.Progress to be tracked in: #1147
Related Discussion: Eclipse Dirigible 6.0
All reactions