aws-samples / aws-samples/amazon-chime-sdk
Request for documentation on integrating the React Meeting Demo into an existing app
- Dominant language
- TypeScript
- Stars
- 116
- Forks
- 133
- PR merge metrics
- No merged PRs in 30d
Description
### What demo do you have issue with?
React Meeting Demo
### How can the documentation be improved to help your use case?
I have an existing React app and I copied the folder `apps/meeting/src` into my react app. I am now trying to use the individual components in the folder `apps/meeting/src/components` in the react app but it fails to bundle when I bundle the whole app (existing app + the meeting app).
The bundling fails with errors such as below:
```
[ERROR] Could not resolve "fs"
node_modules/@smithy/shared-ini-file-loader/dist-cjs/getSSOTokenFromFile.js:4:21:
4 │ const fs_1 = require("fs");
╵ ~~~~
The package "fs" wasn't found on the file system but is built into node. Are you trying to bundle
for node? You can use "--platform=node" to do that, which will remove this error.
```
As suggested, the bundling works when specifying the `--platform=node` flag. In essence, when trying to bundle the app for the browser, the bundling process fails. But when trying to bundle the app for node, the bundling process succeeds. I have not been able to get around this issue easily.
Would you be able to provide documentation on developers can integrate the React meeting demo app into their existing React app? This would be really useful!
### What documentation have you looked at so far?
I went through the documentation on running the React meeting demo app. I also looked at external documentation on using esbuild and webpack. These haven't been super-useful as my issue is with integrating the React meeting demo app into the existing React app.
Thank you so much for your time and help!
Contributor guide
Research direction
Start by reviewing the React Meeting Demo under apps/meeting/src, especially apps/meeting/src/components, and reproduce the browser bundling failure when those components are copied into an existing React app. Documentation is done when it explains the supported integration path and how to bundle the meeting components for the browser without the reported fs resolution failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- documentation, frontend, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100