@stefano22/testapp v1.0.2

updated image webpack loader to the latest release within this version

^ ---- latest stable release within this major version

• ---- latest release within this major version

semantic versioning (semver)

(as the publisher of a package)

• package starting with zero means that your package isn't yet stable for initial release, when is ready for people to depend on it, and its functionality then starts with 1.0.0

• for minor fixes (minor bug fix), where changes don't break anything nor add any new features, then is a patch release 1.0.1

• minor releases add some functionality, so you increment the middle number 1.1.1

• a change to the api that it's not backwards compatible, then you have a major release. 2.0.0

  (as the user of a package)

  • what kind of updates you want to accept

  lets say you just want to accept patch changes

         1.0.0  -->  1.0.1
         1.0.0  -|-> 1.1.0
  
         //can be indicated in package.json file in a few different ways:
          1.0
          1.0.x   //an x in the place of the patch number
         ~1.0.4   //a tilda in front of the exact number

     //or download new features but nothing that is backwards incompatible

      1
      1.x   //an x in the place of the patch number
     ^1.0.4   //a tilda in front of the exact number

#### do a patch with npm

- npm version patch
- npm publish
- npm publish --access=public

#### private packages in npm have a @scope
- usually @username/name-of-package
- npm init --scope=stefano22