@nativescript-community/ui-cameraview
    Preparing search index...

    @nativescript-community/ui-cameraview

    @nativescript-community/ui-cameraview

    Downloads per month NPM Version

    A CameraView allowing custom live processing for NativeScript


    iOS Demo Android Demo

    Run the following command from the root of your project:

    ns plugin add @nativescript-community/ui-cameraview

    IMPORTANT: Make sure you include xmlns:mdc="@nativescript-community/ui-cameraview" on the Page element

    
        
            
       
    
    

    import { registerElement } from 'nativescript-angular/element-registry';
    import { CameraView } from '@nativescript-community/ui-cameraview';
    registerElement('CameraView', () => CameraView);
    <CameraView width="100" height="100"></CameraView>
    

    import Vue from 'nativescript-vue';
    (<any>Vue).registerElement('CameraView', () => require('@nativescript-community/ui-cameraview').CameraView);
    <CameraView  width="100" height="100"/>
    

    This repository includes Svelte demos. In order to run these execute the following in your shell:

    $ git clone https://github.com/@nativescript-community/ui-cameraview
    $ cd ui-cameraview
    $ npm run i
    $ npm run setup
    $ npm run build
    $ cd demo-svelte
    $ ns run ios|android

    The repo uses submodules. If you did not clone with --recursive then you need to call

    git submodule update --init
    

    The package manager used to install and link dependencies must be pnpm or yarn. npm wont work.

    To develop and test: if you use yarn then run yarn if you use pnpm then run pnpm i

    Interactive Menu:

    To start the interactive menu, run npm start (or yarn start or pnpm start). This will list all of the commonly used scripts.

    npm run build.all
    

    WARNING: it seems yarn build.all wont always work (not finding binaries in node_modules/.bin) which is why the doc explicitly uses npm run

    npm run demo.[ng|react|svelte|vue].[ios|android]

    npm run demo.svelte.ios # Example

    Demo setup is a bit special in the sense that if you want to modify/add demos you dont work directly in demo-[ng|react|svelte|vue] Instead you work in demo-snippets/[ng|react|svelte|vue] You can start from the install.ts of each flavor to see how to register new demos

    You can update the repo files quite easily

    First update the submodules

    npm run update
    

    Then commit the changes Then update common files

    npm run sync
    

    Then you can run yarn|pnpm, commit changed files if any

    npm run readme
    
    npm run doc
    

    The publishing is completely handled by lerna (you can add -- --bump major to force a major release) Simply run

    npm run publish
    

    The repo uses https:// for submodules which means you won't be able to push directly into the submodules. One easy solution is t modify ~/.gitconfig and add

    [url "ssh://git@github.com/"]
    pushInsteadOf = https://github.com/

    If you have any questions/issues/comments please feel free to create an issue or start a conversation in the NativeScript Community Discord.

    The repo uses submodules. If you did not clone with --recursive then you need to call

    git submodule update --init
    

    The package manager used to install and link dependencies must be pnpm or yarn. npm wont work.

    To develop and test: if you use yarn then run yarn if you use pnpm then run pnpm i

    Interactive Menu:

    To start the interactive menu, run npm start (or yarn start or pnpm start). This will list all of the commonly used scripts.

    npm run build.all
    

    WARNING: it seems yarn build.all wont always work (not finding binaries in node_modules/.bin) which is why the doc explicitly uses npm run

    npm run demo.[ng|react|svelte|vue].[ios|android]

    npm run demo.svelte.ios # Example

    Demo setup is a bit special in the sense that if you want to modify/add demos you dont work directly in demo-[ng|react|svelte|vue] Instead you work in demo-snippets/[ng|react|svelte|vue] You can start from the install.ts of each flavor to see how to register new demos

    You can update the repo files quite easily

    First update the submodules

    npm run update
    

    Then commit the changes Then update common files

    npm run sync
    

    Then you can run yarn|pnpm, commit changed files if any

    npm run readme
    
    npm run doc
    

    The publishing is completely handled by lerna (you can add -- --bump major to force a major release) Simply run

    npm run publish
    

    The repo uses https:// for submodules which means you won't be able to push directly into the submodules. One easy solution is t modify ~/.gitconfig and add

    [url "ssh://git@github.com/"]
    pushInsteadOf = https://github.com/

    If you have any questions/issues/comments please feel free to create an issue or start a conversation in the NativeScript Community Discord.