Integration of Current Components into a NPM Package Library

John Peters - Jul 5 '20 - - Dev Community
  • Create a fully separate library project. This prevents mixing of inter-project concerns. It also exposes dependencies.

  • Find all "common" components to put into library, and drop one at a time, into the library. Compile and Work out dependency issues.

  • Publish to NPM early and often.

  • Start importing components back into original project. Remove the old pre migrated components one at a time.

  • Compile source project fixing all dependencies.

  • Repeat until there are no client side install issues, and the common code you want, is migrated completely to the library.

Be Patient

This is a very tedious process full of npm traps. If you are not an NPM expert, you will become one.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player