Project A
contains a few functions and data models I use in diff't repos
, all tied to the same product. I'd like to turn them into an npm module
, but without extracting the code from project A
.
When I see other modules
on npm
, they generally tie to a github repo
that contains all the source code, as well as a full stack to run/modify the module.
Does this mean I have to extract the code from project A
into its own repository, build/configure a stack to allow it to run in isolation from project A
, and then import
it back into project A
& other projects?
Or is it possible to just export the functions w/o a full stack, and without moving the code from my main project
?
an attempt to pre-empt 'duplicate' comments:
this Q talks about working with an existing module, which doesn't answer my concern, as it has to do w/ worrying about pull requests
being merged on time
npm link
, discussed here, looks like it'd do the trick if I'd already extracted the code from the project, but I'd like to avoid that.