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
To avoid the complexity and make it easier to maintain the backframe packages, a decision was made to abandon commonjs in favor of esmodules. Initial versions of backframe included double compilation targets but this proved difficult to maintain. For a package like express, it is easy to stick with commonjs since the end users only import the package itself. But with backframe, it's a little bit more complicated since the end user not only imports backframe packages and utils, but the packages themselves also import the user's code. For this to work seamlessly, we went with esmodules
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
Uh oh!
There was an error while loading. Please reload this page.
-
To avoid the complexity and make it easier to maintain the backframe packages, a decision was made to abandon commonjs in favor of esmodules. Initial versions of backframe included double compilation targets but this proved difficult to maintain. For a package like express, it is easy to stick with commonjs since the end users only import the package itself. But with backframe, it's a little bit more complicated since the end user not only imports backframe packages and utils, but the packages themselves also import the user's code. For this to work seamlessly, we went with esmodules
Beta Was this translation helpful? Give feedback.
All reactions