TypeScript icon, indicating that this package has built-in type declarations

2.12.45 • Public • Published


Salla Core JS

Kick off your Salla JS project with this core package. It includes the main elements needed for building a JS project. On top of that, it's based on the Event-Driven Architecture.
Explore our blogs »

Report Bug · Request Feature . </Salla Developers> . Official Documentation

Table of Contents
  1. Overview
  2. Getting Started
  3. Usage
  4. Support
  5. Contributing
  6. Credits
  7. License


Salla Core JS package is based on the Event-Driven Architecture, which is a modern design approach centered on data that represents "events" (i.e., a product has been added to the cart). In event-driven programming, an event is the result of a single or multiple actions. Subscribers can listen to that event and take action after it is released by the emitter.

Getting Started

Salla Core JS uses EventEmitter2, which is an implementation of the EventEmitter module found in Node.js. It not only outperforms EventEmitter in benchmarks and is browser-compatible, but it also adds a slew of new non-breaking functionality to the EventEmitter interface.


Salla Core JS can be installed from the npm using the following commands:

npm install @salla.sa/base --save
yarn add @salla.sa/base

What's included?

A quick look at the top-level files in the Salla Core JS project:

├── src / helpers
├── src / config.d.ts
├── src / cookie.ts
├── src / event.js
├── src / index.ts
├── src / logger.ts
└── src / storage.js


import Salla from "@salla.sa/base"

Upon the installation, the following will be available to the developer:


When the JS Core project is first loaded, the initialization procedure is used to obtain the necessary configuration settings. The developer has the ability to configure the project to meet his needs.


The JS Core project is packaged with a variety of helpful functions that may be accessed and used directly within projects.


Developers can use local storage to save and retrieve data in the browser. The data in local storage does not have an expiration date. This means that even if the tab or browser window is closed, the data will remain. Furthermore, the data is only saved locally.


The JS Core project makes it easy to create, retrieve, and modify cookies. Name, value, and length can be limited.


The JS Core project includes a logger tool that helps in tracking the execution flow and determining why certain things occur in the JS application.


The Events can be triggered by the emitter's 'emit()' method. This method causes the event to be pushed using the data that the developer has provided.

For example, the developer may create an event based on verified login by the user. Simply, the emit() method can be called with a list of parameters. These parameters state the event's action and the passed data along with it as below:

// via event name
Salla.event.emit("auth::verified",  {success:  true},  'email')

Listening to the event

After creating the event along with its list of data, the next step is to implement an appropriate listener for that event. In Salla JS Events, this can be achieved using two methods:

  • Using the event name and result directly along with an anonymized function to perform the needed action based on the event result.
// via event name
Salla.event.on('auth::verified',(response, authType)  =>  {
// lets do anything when the event emit
console.log('The customer has been verifed');
console.log(response, authType)
  • Adding a one time listener for the event along with an anonymized function to perform the needed action based on the event result.
// Adds a one time listener for the event.
Salla.event.once('auth::verified',(response, authType)  =>  {
// The listener is invoked only the first time
// the event is fired, after which it is removed.
console.log('The customer has been verifed');
console.log(response, authType)

(back to top)


The team is always here to help you. Happen to face an issue? Want to report a bug? You can submit one here on Github using the Issue Tracker. If you still have any questions, please contact us via the Telegram Bot or join in the Global Developer Community on Telegram.

(back to top)


Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

(back to top)


(back to top)


The MIT License (MIT). Please see License File for more information.

(back to top)


DownloadsWeekly Downloads






Unpacked Size

463 kB

Total Files


Last publish


  • eslamoo
  • jalmatari
  • nabute
  • s.alkhwlani