-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm package not in registry #2
Comments
Yes 😢 See here I'm waiting for a response to my NPM ticket before finding a new name or publishing as a scoped package. In the meantime you can (just as easily) do this: $ yarn add lukeed/deepset
#=> pulls from github directly |
thanks |
Now published as |
lukeed
added a commit
that referenced
this issue
Oct 25, 2023
* fix: TS .d.ts resolution (#1) There are types at '/node_modules/dset/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'dset' library may need to update its package.json or typings.ts(7016) * Update package.json (#2) * Simplified package exports * Updated back to original repo * Update package.json --------- Co-authored-by: Luke Edwards <luke.edwards05@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: