@snugdesk/whatsapp-widget 0.2.2 → 0.2.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -30
- package/fesm2022/snugdesk-whatsapp-widget.mjs +63 -1935
- package/fesm2022/snugdesk-whatsapp-widget.mjs.map +1 -1
- package/index.d.ts +12 -1103
- package/package.json +8 -10
package/README.md
CHANGED
|
@@ -25,12 +25,6 @@ npm install @snugdesk/core
|
|
|
25
25
|
npm install @snugdesk/whatsapp-widget
|
|
26
26
|
```
|
|
27
27
|
|
|
28
|
-
The widget expects the host app to provide Amplify packages (peer dependencies). This library supports Amplify v5 only. If your app does not already use Amplify, install them explicitly:
|
|
29
|
-
|
|
30
|
-
```bash
|
|
31
|
-
npm install aws-amplify@^5 @aws-amplify/api-graphql@^3
|
|
32
|
-
```
|
|
33
|
-
|
|
34
28
|
Other runtime dependencies are bundled (`@aws-sdk/client-s3`, `@ctrl/ngx-emoji-mart`, `ngx-avatars`, `ngx-infinite-scroll`, `ngx-skeleton-loader`, `moment-timezone`, `libphonenumber-js`, `sort-nested-json`, `uuid`, …).
|
|
35
29
|
|
|
36
30
|
---
|
|
@@ -172,28 +166,6 @@ Ensure you render the widget only after you have a fresh token to avoid the comp
|
|
|
172
166
|
|
|
173
167
|
---
|
|
174
168
|
|
|
175
|
-
## 🧩 Amplify Configuration Behavior
|
|
176
|
-
|
|
177
|
-
The widget can run in two modes without any extra setup from third parties:
|
|
178
|
-
|
|
179
|
-
- If the host already configured Amplify and its AppSync endpoint matches the widget default (`defaultAppSyncConfig.endpoint`), the widget will **reuse the host config** and **skip** `Amplify.configure`.
|
|
180
|
-
- The widget honors the host AppSync auth mode when it reuses the host config (for example, `API_KEY` vs `AWS_LAMBDA`).
|
|
181
|
-
- Otherwise, the widget will **configure Amplify itself** using its default configuration (`AWS_LAMBDA`).
|
|
182
|
-
|
|
183
|
-
You can also pass your host Amplify config directly to the widget:
|
|
184
|
-
|
|
185
|
-
```ts
|
|
186
|
-
import { provideAmplifyConfig } from '@snugdesk/whatsapp-widget';
|
|
187
|
-
import { AmplifyConfig } from './app/app-config.model';
|
|
188
|
-
|
|
189
|
-
@NgModule({
|
|
190
|
-
providers: [provideAmplifyConfig(AmplifyConfig)]
|
|
191
|
-
})
|
|
192
|
-
export class AppModule {}
|
|
193
|
-
```
|
|
194
|
-
|
|
195
|
-
---
|
|
196
|
-
|
|
197
169
|
## 🎨 Assets & Styling
|
|
198
170
|
|
|
199
171
|
The library bundles icons, background artwork, and shared CSS under `@snugdesk/whatsapp-widget/assets`. To make them available during your build, add the folder to the Angular CLI asset list:
|
|
@@ -241,9 +213,8 @@ If you already use custom asset pipelines, copy the contents of `node_modules/@s
|
|
|
241
213
|
|
|
242
214
|
## 🛠 Troubleshooting & Tips
|
|
243
215
|
|
|
244
|
-
- A missing or expired token results in `Missing authentication token for AppSync request.` in the console. Refresh the token and re-render the widget.
|
|
245
216
|
- When adjusting the asset output path, make sure the relative URLs in the generated CSS still resolve (keep `/assets/snugdesk-whatsapp/...` in the final build).
|
|
246
|
-
- Upgrade the widget in lockstep with your Angular major version to stay within the supported peer dependency range (`>=
|
|
217
|
+
- Upgrade the widget in lockstep with your Angular major version to stay within the supported peer dependency range (`>=19.0.0`).
|
|
247
218
|
|
|
248
219
|
---
|
|
249
220
|
|