npm-package
Npm is a package manager for JavaScript, included with Node.js. As a package manager, npm makes it easy for developers to share and reuse code.
Here are 3,589 public repositories matching this topic...
-
Updated
Sep 20, 2020 - TypeScript
I've read many similar closed issues, but haven't found a good documented solution on what can I do as a consumer of ky package if I need to support e.g iOS 10.0 browser (that breaks on async/await support currently).
I agree that it's not related to ky itself, but can be a nice help for the consumers of the package.
In our particular can we don't use babel (we use typescript), so I'm
-
Updated
Sep 23, 2020 - JavaScript
-
Updated
Jun 19, 2020 - JavaScript
-
Updated
Sep 28, 2020 - JavaScript
-
Updated
Jul 8, 2020 - JavaScript
-
Updated
Nov 1, 2019 - JavaScript
-
Updated
Sep 28, 2020 - TypeScript
-
Updated
May 28, 2019 - JavaScript
Please describe what the rule should do:
Using the tag property for RouterLink or NuxtLink is usually a bad idea because it removes out-of-the-box accessibility (further: vuejs/vue-router-next#148 (comment)). This rule should throw an error if people try to change the tag.
PS: The tag prop will be removed in future majors of vue-router.
Hi, im trying to use Hashids with Typescript and Node.
import Hashids from 'hashids';
I'm not getting any Typescript errors in the editor, but Im getting this error when the code is compiled.
Using ts-node version 8.5.4, typescript version 3.7.5
`Error: No valid exports main found for 'node_modules\hashids'
at resolveExportsTarget (internal/modules/cjs/loader.js:625:9)
-
Updated
Sep 15, 2020 - TypeScript
My goal is to have the best documentation for each provided type.
If something is unclear in any of the types, please comment or open a PR to improve it.
Some things you could contribute:
- Fix typos.
- Improved description of the type.
- More examples.
- Provide more real-world use-cases. This helps the user understand where a type might come in handy.
- Add links to relevant discu
Fix the browsers!
The goal of this project is to make itself obsolete. We should try to get browsers to fix their own styles so we don't have to work around them indefinitely.
If you want to help out:
- Pick a style in
modern-normalize.css - Go to the relevant browser issue trackers ([Chrome](http://dev.chromium.org/for-test
-
Updated
Jan 28, 2019 - JavaScript
-
Updated
Sep 25, 2020 - JavaScript
-
Updated
Jun 22, 2020 - JavaScript
-
Updated
Mar 23, 2018 - JavaScript
For popular things that makes sense. Suggestions welcome, but I'm not going to add more than maybe 30. So make it worth it.
Don't do a PR. I'll add them all at once when we've decided on what to include.
-
Updated
Sep 21, 2020 - JavaScript
-
Updated
Sep 27, 2020 - JavaScript
-
Updated
Sep 24, 2020 - JavaScript
-
Updated
Sep 27, 2020 - JavaScript
-
Updated
Sep 21, 2020 - JavaScript
The TS typing does not describe the properties of error classes.
For example with the KafkaJSProtocolError class. This error class have two properties : type and code. This two properties are set in the constructor.
class KafkaJSProtocolError extends KafkaJSError {
constructor(e) {
super(e, { retriable: e.retriable })
this.type = e.type
this.code = e.c-
Updated
Sep 20, 2020 - JavaScript
-
Updated
Sep 23, 2020
Created by Isaac Z. Schlueter
Released January 12, 2010
- Organization
- npm
- Website
- www.npmjs.com
- Wikipedia
- Wikipedia


Preview links are not appearing for me because my CI/CD adds github metadata in the canonical location, but the github integration looks elsewhere.
Describe the bug
Currently, the Github integration looks at a commit status's contexts for a deploy url. The thing is, the canonical way to specify a deploy url is using environment deployments. So I think the integration should look at the e