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
When publishing a NAOT node package with dotnet utility on Linux or Mac, the Common JS loader for the library has a syntax error: const moduleName = path.basename(__filename, __filename.match(/(/.[cm]?js)?$/)[0]);
On the other hand, when publishing on Windows, there is no error: const moduleName = path.basename(__filename, __filename.match(/(\.[cm]?js)?$/)[0]);
Perhaps it has something to do with the generator using OS-dependent paths in regex (when it should not)?
Thanks
The text was updated successfully, but these errors were encountered:
Oh, that's odd. It seems to be some strange behavior of MSBuild WriteLinesToFile, which is used to apply some transformations to that file when publishing as AOT. I'll figure out a workaround.
Hello,
When publishing a NAOT node package with dotnet utility on Linux or Mac, the Common JS loader for the library has a syntax error:
const moduleName = path.basename(__filename, __filename.match(/(/.[cm]?js)?$/)[0]);
On the other hand, when publishing on Windows, there is no error:
const moduleName = path.basename(__filename, __filename.match(/(\.[cm]?js)?$/)[0]);
Perhaps it has something to do with the generator using OS-dependent paths in regex (when it should not)?
Thanks
The text was updated successfully, but these errors were encountered: