-
|
I try to weave CLR assemblies (i.e. written in CSharp for dotnet) with Theia for the backend. Error: The edge module has not been pre-compiled for node.js version v20.18.0. You must build a custom version of edge.node. Please refer to https://github.com/agracio/edge-js for building instructions. But the pre-compiled files already exist:
Is there a trick to inform the Theia build&run tools to include/load the specific files? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
Hey @cbries, we compile/bundle our backend with webpack to minimize disk usage and startup time. Since this changes the way the files are layouted on disk, this check done by edge.js fails. There are two ways to go about this:
|
Beta Was this translation helpful? Give feedback.
-
|
@msujew thanks -- the issue vanished by deleting "node_modules" in the root folder and subsequent call of |
Beta Was this translation helpful? Give feedback.
-
|
@msujew Unfortunately I still have trouble. During build I do get several error messages: When I add an Warnings:
In the end I do get errors: I copy the node/assembly files to the relevant directory:
And so on and so on... When I create a simple webpack-Project, everything works fine and edge-js loads. Most of all github sources uses objects as well.... https://github.com/search?q=module.exports+language%3AJavaScript+&type=code I am puzzled 😒 |
Beta Was this translation helpful? Give feedback.
-
|
In addition, debugger does not attach as well with vscode very often... Probably just on my machine :) |
Beta Was this translation helpful? Give feedback.
-
|
The array is just there so we can instruct webpack to perform multiple builds at the same time. We have multiple bundles that we create for different runtimes (e.g. browser and node), which require different build configurations. Most projects simply don't have that requirement. As for |
Beta Was this translation helpful? Give feedback.
-
|
@msujew The hidden secret for me was that My module.exports = [
...configs,
{
...nodeConfig.config,
externals: {
'edge-js': 'commonjs2 edge-js',
}
}
];My sample based on the @injectable()
export class HelloBackendServiceImpl implements HelloBackendService {
sayHelloTo(name: string): Promise<string> {
try {
const callDotnet = edge.func({
assemblyFile: 'assets/PrimeNumberNet.dll'
});
callDotnet(12, function (error, result) {
if (error) throw error;
console.log('callDotnet: ' + result);
});
} catch (err) {
console.log(err);
}
return new Promise<string>(resolve => resolve('Hello ' + name));
}
}Result:
|
Beta Was this translation helpful? Give feedback.
-
|
Perfect, glad to help :) |
Beta Was this translation helpful? Give feedback.
Hey @cbries,
we compile/bundle our backend with webpack to minimize disk usage and startup time. Since this changes the way the files are layouted on disk, this check done by edge.js fails.
There are two ways to go about this:
webpack.config.jsof your app). This is quick and dirty but should work well.webpack.config.js) to copy the native.nodefiles to the expected location. It looks like edge.js expects them under<app>/lib/backend/native/win32/x64/20/<file>.