- 
                Notifications
    You must be signed in to change notification settings 
- Fork 10.5k
[Blazor] Finalize the integration between runtime and Blazor #49385
New issue
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
Conversation
…o match newer emscripten
| @javiercn @MackinnonBuck The CI will fail until changes from runtime flow to aspnetcore, but I would appreciate your feedback sooner, ideally to make it to preview7. | 
        
          
                src/Components/WebAssembly/WebAssembly/src/Services/LazyAssemblyLoader.cs
          
            Show resolved
            Hide resolved
        
      | if (startOptions.loadBootResource) { | ||
| const resourceType: WebAssemblyBootResourceType = 'dotnetjs'; | ||
| const customSrc = startOptions.loadBootResource(resourceType, dotnetJsResourceName, src, dotnetJsContentHash); | ||
| const customSrc = startOptions.loadBootResource(resourceType, 'dotnet.js', src, ''); | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is possible a breaking change, because we don't have a hash of dotnet.js anymore, but I'm sure if there is a case where it was usable when providing only URL for script
out&errfunctionsCloses dotnet/runtime#87178