mirror of
https://github.com/Alfresco/alfresco-ng2-components.git
synced 2025-09-17 14:21:29 +00:00
72704cad57
* change prepublish to build only add .npmrc in the gitignore and npmignore clean .npmrc during the clean task change registry during publish with npmrc file add rimraf install in npm publish * add option to link an alfresco-js-api from github * npm build on develop branch will use the alfresco-js-api from develop * modify script after review add -gitjsapi to starts.sh to change jsapi pointing add -vjsapi to starts.sh to change jsapi pointing * start dist demo shell script option
Alfresco Angular 2 Components
Base components
- Material Design elements
- Context Menu component
ECM components
- DataTable
- DocumentList
- Login
- Search
- Social
- Tag list and controls
- User Info
- Upload
- Viewer
- Webscript Viewer
BPM components
You can browse all the components at the following address:
http://devproducts.alfresco.com/
How to test a change to a generic component in its own demo
Let's suppose that for some reason you have changed a component and you want to test this changes. The example is based on the ng2-alfresco-login component, but you can use the same steps for any component.
- Move inside the component folder and link it.
cd ng2-alfresco-login
npm link
- Build the component with the watcher enabled.
npm run build:w
- From another terminal move inside the demo sub folder and link the component to the local node_modules folder.
cd demo
npm link ng2-alfresco-login
- Start the demo project.
npm run start