Package new component

[Amr7]

Hi team,

I created a custom component and added it to suitecrm\core\app\core\src\lib\components\navbar\x, and it’s working fine.

So how I can package this component to share it on store.suitecrm

It will need to add the new files to the components path and run yarn run build:core in the project.

[rsp]

If it is module, I think you can use studio to export it.

Module Installer

---

Front-end Developer Install Guide - 8.8.0+

---

Selling | SuiteCRM Store

[pgr]

You shouldn’t be making any custom work directly under core, it should be under extensions folder.

The documentation explains this.

[Amr7]

Hi @rsp
Thanks for your reply. I need to package it for v8, and I believe the Module Installer is for v7, right?
Also, if it’s for v7, do you know if it will work with v8?

Hi @pgr
Thanks for your reply. So I need to create an extension to add this custom component, correct?
Also, I reviewed the extensions developer page, and it seems to be for creating extensions within specific pages. Do you know how I can create one for my custom core/navbar component?

[pgr]

I am not sure of the details because I haven’t done front-end custom work myself in v8 (apart from some minor tweaks).

Maybe have a look at this thread or ask the people there:

Front end extensions cant build

I have read the docs on how to create an extension module which I did by cloning defaultExt and renaming references. But now I want to compile it and watch for changes but none of the build or watch commands work. Error: This command is not available when running the Angular CLI outside a workspace. I cant understand how to do this correctly. I want to create an extension module for each core/base module and I am just struggling to get this part to work.

[Amr7]

This is for rebuilding the project after adding the extension.
I have already created a custom component in the navbar and just need to know how to package it.

[rsp]

Add extension in the navbar

Run the Build Commands Sequentially: Build the frontend common, core, and shell packages in the specified order. Execute the following commands one by one: yarn run build:common yarn run build:core yarn run build:shell Here’s a brief explanation of what each command does: yarn run build:common: This command builds the common package, which likely contains shared components, utilities, or libraries used across other parts of your project. yarn run build:core: This command builds the core pack…

[Amr7]

I already created the component, and it’s running and working fine. No problems.

My question is: how can I package it so that anyone can install it in their SuiteCRM account?

[rsp]

Ohh I do not know it. Are you planning to create an add-on?

[Amr7]

Yes, exactly. I need to create an add-on or something similar so I can upload it to SuiteCRM Store.

[rsp]

I think your best chance will be to contact once of the developer team on the store and ask them. Some add-ons supports v8.x.

I think those teams are on the forum too. You can send them email.

[pgr]

I would give a straight answer if I had one (I don’t), but I question your statement that it’s already done, just needs packaging.

Maybe it needs done differently so it fits the SuiteCRM architecture, and that’s the extensions folder and defaultExt, as far as I know…

[rsp]

How to add front-end framework customization into the suitecrm installable package?

Hello there, We had created a suitecrm product, compatible with version suitecrm 7. Now, we are working to be compatible with suitecrm 8. but the problem is how will I deliver that product to the customer? I have noticed that If I am doing any customization then I have to create a front-end extension. But I’m not sure how to deliver this extension in installable product zip. Can anyone help me with this? @clemente.raposo @pgr @abuzarfaris @domiserver @Will @samus-aran @amariussi @pstevens @g…

Looks like even other person has similar question

[Amr7]

So has anyone here created a complete extension/add-on/plugin before and uploaded it to the SuiteCRM Store?