Exports in package.json seem too restricted #171
Unanswered
ehg-fblenkle
asked this question in
Q&A
Replies: 1 comment
-
|
The main reason it's not exported is that anything that is "public" should be maintained and kept without breaking changes. Keeping internals, well internal, makes it easier for internal development without documenting any breaking changes it can cause. I think in your case I would just fork the repository, you're not planning to use it as it is, you want to build something custom. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey,
I need to develop my own handler against redis (for reasons, see #169). But it's very hard, because I cannot import the types/utils I need. At first I thought it would be sufficient to "grant access" to types of cache-handler-types.d.ts, but as I developed against a "patched version" I realized I also need some utils (e.g. convertStringsToBuffers).
I'm not used to have these issues when dealing with other packages, so I wanted to ask if there is a reason for these strict exports.
Beta Was this translation helpful? Give feedback.
All reactions