We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are use-cases when there is no main javaScript file. For example with NextJs where we don't own application startup.
src\mono\wasm\build\WasmApp.targets
<Error Condition="'$(WasmMainJSPath)' == ''" Text="%24(WasmMainJSPath) property needs to be set" />
src\tasks\WasmAppBuilder\WasmAppBuilder.cs
if (!File.Exists(MainJS)) throw new LogAsErrorException($"File MainJS='{MainJS}' doesn't exist.");
The text was updated successfully, but these errors were encountered:
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
if (!string.IsNullOrEmpty(MainJS) && !File.Exists(MainJS)) throw new LogAsErrorException($"File MainJS='{MainJS}' doesn't exist.");
arch-wasm, area-Build-mono
arch-wasm
area-Build-mono
Sorry, something went wrong.
cc @radical @danroth27
I hit this as well when looking at using .NET from existing JS apps: #77191
WasmMainJSPath
pavelsavara
Successfully merging a pull request may close this issue.
There are use-cases when there is no main javaScript file.
For example with NextJs where we don't own application startup.
src\mono\wasm\build\WasmApp.targets
src\tasks\WasmAppBuilder\WasmAppBuilder.cs
The text was updated successfully, but these errors were encountered: