You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
I have forked a library named "A" and made some modifications. I've renamed this modified version as "@my/A". To ensure backward compatibility in projects that use this library, I have set up the dependency in package.json as:
"dependencies": {
"A": "npm:@my/A@^10.0"
}
This way, all the code that uses this library does not need to be modified. However, the issue I'm facing is the auto-linking mechanism, "@my/A" gets symlinked to its source directory instead of "A", which causes the library not to be found. I could change the code to directly use "@my/A", but there are many usages, and I believe there should be a better solution.
Is there a solution for this kind of issue? Thanks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi there,
I have forked a library named "A" and made some modifications. I've renamed this modified version as "@my/A". To ensure backward compatibility in projects that use this library, I have set up the dependency in package.json as:
This way, all the code that uses this library does not need to be modified. However, the issue I'm facing is the auto-linking mechanism, "@my/A" gets symlinked to its source directory instead of "A", which causes the library not to be found. I could change the code to directly use "@my/A", but there are many usages, and I believe there should be a better solution.
Is there a solution for this kind of issue? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions