Error: Unexpected path .DS_Store at validatePath (/Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/get-definitely-typed.ts:256:15) at DiskFS.getPath (/Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/get-definitely-typed.ts:217:13) at DiskFS.isDirectory (/Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/get-definitely-typed.ts:227:33) at /Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/parse-definitions.ts:35:131 at /Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/util/util.ts:56:34 at initArray (/Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/util/util.ts:114:18) at nAtATime (/Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/util/util.ts:51:23) at Object.filterNAtATimeOrdered (/Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/util/util.ts:88:42) at Object.parseDefinitions [as default] (/Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/parse-definitions.ts:35:32) at main (/Users/cwd/src/DefinitelyTyped/node_modules/types-publisher/src/tester/test.ts:24:5)
1> apple-mapkit-js failing: 1> SyntaxError: Unexpected token } in JSON at position 82 1> at JSON.parse (<anonymous>) 1> at Object.<anonymous> (/Users/cwd/src/DefinitelyTyped/node_modules/dtslint/bin/util.js:19:21) 1> at Generator.next (<anonymous>) 1> at fulfilled (/Users/cwd/src/DefinitelyTyped/node_modules/dtslint/bin/util.js:4:58)
Error: In package.json: Dependency @vue/test-utils not in whitelist. If you are depending on another `@types` package, do *not* add it to a `package.json`. Path mapping should make the import work. If this is an external library that provides typings, please make a pull request to types-publisher adding it to `dependenciesWhitelist.txt`.
Whereas I didn't change anything related to that. Should I rebase on upstream or is there anything more ?
@vue/test-utilsstarted after my PR got merged in. (Which was also a stale cache issue, but I'm not sure why it's still an issue or what will take to resolve it for everyone.) DefinitelyTyped/DefinitelyTyped#37655
.d.tsfor firstname.lastname@example.org. Was wondering if there is an automatic build for this or if I should submit a pr? Looking to use v8.serialize/deserialze functions that are in the newer commits
Hi, I'm trying to do my first PR to add typings for a package, and I need to
import * as fs from 'fs' , however I get "Cannot find module 'fs'." errors (same for 'http', or any other node module, I assume). I looked into other packages and they have the same tsconfig but the import seems to work there. The only way I found to get it to work is to add
/// <reference types="node" />
... is that how i'm supposed to do it?
/// <reference types="node" />is used in a lot of packages if you check here for example. I guess the best thing to do is wait for the PR review and see if it gets approved.
Hi there! I would like to add types for
react-loadable-visibility. Basically it exports the same types as
react-loadable, which is also typed via DefinitelyTyped. I am not sure how to best do this. My best guess is
import Loadable from 'react-loadable'; export default Loadable;
and adding a
package.json with a dependency to
react-loadable. Is this the correct way?
Recently I was playing around with a basic DOM TSX renderer (i.e. a TSX renderer that instead of creating React elements, creates
HTMLElement). It occurred to me that if you do not want to loosen type-checking (for example by turning off
"noImplicitAny"), you need a proper type definition for this, and I could not find such a type definition out there.
My question is, is there any such typing out there, is it under the scope of DefinitelyTyped or not, should something like this even be under that scope? I wrote a basic custom type definition for myself (with stringent attribute checking), but I do not know if it is of proper quality (since I do not know exactly what it should contain to be a proper high-quality type definition for the outlined use-case, couldn't find resources on this as well), and I'm not even sure if something like this would/should be covered by DefinitelyTyped to begin with.
here is a gist of the custom typing I ended up creating for myself, if it helps.
P.S. also any suggestion on how to improve this custom typing regardless of whether or not it should be submitted to DefinitelyTyped is much appreciated.
expressmiddleware where the
resarguments have also been modified/amended from the original
resobjects? I've been having a tough time trying to figure this out unless if those types need to be updated to handle this scenario
knockout.deferred.updateswhich dependes on the removed
knockoutis obsolete since
knockout3.4.0. Should i add a dependency to
@types/knockoutor should this package be removed?