Changes in library (React-Native)

Question

My application uses one npm package (Say x package). I made few changes in one file of x package.

So now i need to manually send that file to other developer's so that they can replace the file of X package. i.e Every time npm install X package get executed on new system, they need to replace that file.

I tried to reach the developer of that npm X package & created pull request but no luck so far.

Query: So do i need to create my one module around the X package or any other workaround. please suggest.

assuming you are using some sort of source control for your project, you can just include the changed files in your commit? With an appropriate message to inform the team — Ryan Turnbull
– Ryan Turnbull, Commented Sep 4, 2017 at 10:24
If x package only depends on JS files then you can copy those JS files from node_modules/x_package folder and copy into your project src code folder, then import components from those files which you have copied, and also you can make changes in those files. — Paras Watts
– Paras Watts, Commented Sep 4, 2017 at 10:35
You should create your own module by cloning it on github and changing some files after that link that directly in package.json so that every time npm install is done nothing will be changed. and see this link to install it stackoverflow.com/questions/17509669/… — Waqas Ahmed
– Waqas Ahmed, Commented Sep 4, 2017 at 10:38
@Waqas thank you for your suggestion. I think you should add this an answer. — Yogesh Lolusare
– Yogesh Lolusare, Commented Sep 12, 2017 at 12:25

Nick · Accepted Answer · 2017-09-04 23:07:18Z

1

In this situation, if you've issued a pull request, you already have a fork of the package's repo, so you have a few options. If you're not sure why your PR isn't being accepted, its probably worth finding out, as that involves the least work for you. Your options:

There are patch managing packages, such as patch-package which are designed to deal with this situation, YMMV depending on your build chain
You could just publish your version to npm, using a name that indicates its a variation of the package, and manage it until your PR is accepted. If you have a private package manager, this might be easiest.
Get your collaborators to use the version of the package you forked (checked out as source), and use something like yalc to install it locally until your PR is accepted. You can use npm link for this, but yarn doesn't handle linking well

answered Sep 4, 2017 at 23:07

Nick

1,82210 silver badges9 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Yogesh Lolusare Over a year ago

Thanks @Nick for your solution. This is helpful.

Waqas Ahmed · Accepted Answer · 2017-09-13 12:15:49Z

1

You should create your own module by cloning it on github and change files that you want and commit them. After that link that repository directly in package.json so that every time npm install is done nothing will be changed. Follow this to link in package.json How to install an npm package from GitHub directly?

edited Sep 13, 2017 at 12:15

answered Sep 13, 2017 at 12:09

Waqas Ahmed

1,4311 gold badge16 silver badges24 bronze badges

Collectives™ on Stack Overflow

Changes in library (React-Native)

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related