Alfresco JS API is archived, how can i integrate a client api code in a non-adf angular project ?

cancel
Showing results for 
Search instead for 
Did you mean: 
4535992
Senior Member

Alfresco JS API is archived, how can i integrate a client api code in a non-adf angular project ?

Jump to solution

NOTE: I recently started developing with angular , so I don't know if the integration of NX into Alfresco projects makes my question "stupid."

The "Alfresco JavaScript API" (https://github.com/Alfresco/alfresco-js-api) project was set as "archived" and transferred to the "Alfresco NG2 Components" (https://github.com/Alfresco/alfresco-ng2-components) project.

I was using the "alfresco-js-api" library to build Alfresco a simple rest api clients on external angular projects separate from the ADF and its components.

Can I still do this ? Only the code allocation on github has changed ? Can i still install create a Alfresco client as a separate project from npm as I did before with the command `npm install @alfresco/js-api` ?  or am I forced to use the ng2-components library directly `@alfresco/alfresco-ng2-components` ?

If in a non-ADF angular project I wanted to create a client rest api do I have to use @alfreco/ng2-components ?

 

1 Solution

Accepted Solutions
4535992
Senior Member

Re: Alfresco JS API is archived, how can i integrate a client api code in a non-adf angular project

Jump to solution

Response by Denys on  this post: https://hub.alfresco.com/t5/application-development/alfresco-js-api-is-archived-how-can-i-integrate-...

Only the physical location of the source code files changed. The library is still published to NPM as usual

View solution in original post

1 Reply
4535992
Senior Member

Re: Alfresco JS API is archived, how can i integrate a client api code in a non-adf angular project

Jump to solution

Response by Denys on  this post: https://hub.alfresco.com/t5/application-development/alfresco-js-api-is-archived-how-can-i-integrate-...

Only the physical location of the source code files changed. The library is still published to NPM as usual