Developers packaging the IVS player into an app are required to resolve and import the following assets via URL:
- ‘amazon-ivs-player/dist/assets/amazon-ivs-wasmworker.min.wasm’
- ‘amazon-ivs-player/dist/assets/amazon-ivs-wasmworker.min.js’;
These assets must not be re-compiled during packaging. Your build tool must ignore these wasm files.
A sample of webpack config can be found: https://github.com/aws-samples/amazon-ivs-player-web-sample/blob/master/webpack.config.js , however, other packagers could have their own way of ignoring certain files from being re-compiled.
Hello,
Adding on to what Riley mentioned, this GitHub issue on our web samples repo seems to describe a similar problem and may have more tips: https://github.com/aws-samples/amazon-ivs-player-web-sample/issues/4.
I'm not familiar with angular-cli, but perhaps you could use this library to specify an additional webpack configuration that'd let you copy the player's assets without recompilation? https://github.com/just-jeb/angular-builders
Best,
Tony
Relevant questions
Adding Server-side rendering and AWS Cognito Identity to an Angular Single Page Application
asked 6 months agoProblems using the GameLift SDK with custom protobuf version
asked 3 years agoWhat API path should Angular use in LightSail? Can't make API calls.
asked a month agoI am trying to log in through the Cognito hosted UI. I don't see such a function in the example, what should I do?
Accepted Answerasked a month agoCan I use glue interactive sessions with pythonshell?
asked 6 months agoCan I use the 'WITH' clause in Athena UNLOAD
asked a month agoAdd server side rendering to Angular/Amplify app
asked 4 years agoSmall Scale VOD Streaming - Am I looking in the right place?
asked 4 months agoIVS player for Angular
asked 2 years agoRedirect after login with aws-amplify/ui-angular 2.0
asked 7 months ago