openvidu/meet-ce/frontend/projects/shared-meet-components
Carlos Santos 45ef1f53b1 Refactor imports in shared-meet-components to use relative paths
- Updated import paths in meeting.component.ts, room-recordings.component.ts, view-recording.component.ts, and other service files to use relative paths instead of absolute paths.
- Removed the '@openvidu-meet/shared/*' path mapping from tsconfig.json.
- Added shared-meet-components to pnpm workspace and updated pnpm-lock.yaml to reflect the changes.
2025-10-20 13:56:14 +02:00
..
2025-10-15 17:42:04 +02:00
2025-10-15 17:42:04 +02:00
2025-10-15 17:42:04 +02:00
2025-10-15 17:42:04 +02:00

SharedMeetComponents

This library was generated with Angular CLI version 18.2.0.

Code scaffolding

Run ng generate component component-name --project shared-meet-components to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project shared-meet-components.

Note: Don't forget to add --project shared-meet-components or else it will be added to the default project in your angular.json file.

Build

Run ng build shared-meet-components to build the project. The build artifacts will be stored in the dist/ directory.

Publishing

After building your library with ng build shared-meet-components, go to the dist folder cd dist/shared-meet-components and run npm publish.

Running unit tests

Run ng test shared-meet-components to execute the unit tests via Karma.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.