@dac-software/phone-number v1.2.3

#Phone Number This is phone number logic app. It can be applied to qarson pl and fr. Library uses react, typescript, css written in SASS preprocessor.

Developing bundler is webpack.

Build production build made as simple tsc compilation with asset files copies provided

This app have custom event listener 'preparePhoneNumber' which reacts on event passed in GTM script. This event can be dispatched everywhere on website using phonenumber app.

##Requirements

• nodejs v10 +
• npm v6.9.0 +

##Installation: Installing dependencies

npm install

Build production library files

npm run build

• Build task build two types of library entrypoints : "web" - destined to web include (for example by script tag) with all depedencies built in (like react and other third party libraries) "ecma script module" - destined for further bundler processing, it is resolved through simply typescript compiling in package.json statement bash tsc -p tsconfig-prod.json && copyfiles "./lib/*/.!(tsx|ts|d.ts|html)" "dist/esm" -u 1

##Use

Application should be used by placing

<div class="react-root-phone-number"><!-- form --></div>

Second mode allows to "predefine"/"force" phone number to show to client

<div class="react-root-phone-number" data-forced-number=""122.122.122"><!-- form --></div>

Library through ESM exposes PhoneNumber react component

<PhoneNumber forcedNumber={'123.123.123'} />

##Development

Running dev server in standalone mode

npm run start

Running dev mode through bundler in other project. Project should be linked by npm.

npm run build:dev

• build dev emmits files into dist/esm/phone-number without CSS / files extraction, it is determined by webpack condition on compilation mode

Running tests

npm run test

####Codestyle

We are in consonance with standardjs.

Validation codestyle:

npm run codestyle-check-typescript Automatic fix:

npm run codestyle-typescript-fix

####CI (bitbucket pipelines)

Checks codestyles and run tests

##Compilation summary

NPM publishing

NPM publishing manually:

1) Increase version in package.json 2) Npm login with proper username and password

```bash
npm login
```

3) Npm publish (command will trigger prepare npm method which should build files to dist directory)

```bash
npm publish --access=public
```

NPM publishing through bitbucket pipelines:

1) dev tag publish using pipeline named: custom: dev-npm-publish

This pipeline automatically defines branch related tag name, for example :
    ``1.0.0-some-branch-name.0``

2) production tag publish using pipeline named: custom: prod-npm-publish

This pipeline requires what kind of semver tag should be defined for publish. You need to fill additional field in pipeline form and type one of version type :
    - patch
    - minor
    - major