Per Method Packages

[ammoradi]

As you know, lodash has a capability to import modularized sub-packages called per method packages
It is good for you to make this package modularized especially for the independent functionalities.
for example when a project only needs one of these package functionalities e.g. Sheba, it is better to add and import it like this:

yarn add persian-tools.sheba

import Sheba from 'persian-tools.sheba'

this approach is good for minimizing projects bundle size when using this package because many projects don't need all of these package functionalities

[ali-master]

Hi @ammoradi

What a good point, I thought a few days ago to refactor the Persian-Tools in order to convert all modules to a standalone module.

So, My suggestion to do the idea is to use the Lerna. Do you have a better idea?

[ali-master]

For your information, I've created the Persian-Tools organization in the NPM, and in the next release, the Persian-tools package path will be:

$ npm i --save @persian-tools/persian-tools

[ammoradi]

@ali-master I didn't use Lerna yet. I will investigate the ways to do this modularization and will mention here if I find a good way

[ali-master]

I appreciate your help and attention.

[moh3n9595]

If you import or require methods directly, e.g. const sheba = require('persian-tools2/sheba'), only the subset of persian-tools2 your package uses will be bundled in projects that use your package.
So another way can be that.