ES modules support

[coolroman]

Is migration to ESM considered ? I mean "type": "module" in package.json.

There are problems using this library in combination with ES modules based libraries.

If I import a ES modules based library I get this error:

The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("...")' call instead.
To convert this file to an ECMAScript module, change its file extension to '.mts', or add the field "type": "module" to 'package.json'

If I set "type": "module" in my contract's project I get this error running any script with blueprint run:

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /scripts/deploy.ts
require() of ES modules is not supported.
require() of /scripts/deploy.ts from /node_modules/.pnpm/@ton+blueprint@0.21.0_@ton+core@0.56.3_@ton+crypto@3.2.0__@ton+crypto@3.2.0_@ton+ton@13.11.2__xpatvrk3jf337gqa7bbsmwnc7e/node_modules/@ton/blueprint/dist/utils.js is an ES module file as it is a .ts file whose nearest parent package.json contains "type": "module" which defines all .ts files in that package scope as ES modules.
Instead change the requiring code to use import(), or remove "type": "module" from /contract/package.json.

[krigga]

Could you please share your use case? Why do you need blueprint as an ES module?

[IlyaSemenov]

@krigga Why would we not use ES modules? That's the future of Javascript anyway. Modern libraries migrate to it, to name a few:

• vue
• date-fns
• valibot

@coolroman The patch to make compile work in an ESM enabled project is simple:

diff --git a/dist/compile/compile.js b/dist/compile/compile.js
index 182c27ed0bd7ce6c2e4d5078e687ad8d9905e648..02ddd4d99a1b056bccc53c8c89f15dba6b8e1b66 100644
--- a/dist/compile/compile.js
+++ b/dist/compile/compile.js
@@ -28,9 +28,9 @@ async function getCompilablesDirectory() {
     }
     return paths_1.WRAPPERS_DIR;
 }
-function extractCompilableConfig(path) {
+async function extractCompilableConfig(path) {
     // eslint-disable-next-line @typescript-eslint/no-require-imports
-    const mod = require(path);
+    const mod = await import(path);
     if (typeof mod.compile !== 'object') {
         throw new Error(`Object 'compile' is missing`);
     }

Until the library is fixed, this can be applied automatically with pnpm-workspace.yaml:

patchedDependencies:
  "@ton/blueprint": patches/@ton__blueprint.patch