{"action":"created","issue":{"url":"https://api.github.com/repos/DefinitelyTyped/DefinitelyTyped/issues/25748","repository_url":"https://api.github.com/repos/DefinitelyTyped/DefinitelyTyped","labels_url":"https://api.github.com/repos/DefinitelyTyped/DefinitelyTyped/issues/25748/labels{/name}","comments_url":"https://api.github.com/repos/DefinitelyTyped/DefinitelyTyped/issues/25748/comments","events_url":"https://api.github.com/repos/DefinitelyTyped/DefinitelyTyped/issues/25748/events","html_url":"https://github.com/DefinitelyTyped/DefinitelyTyped/issues/25748","id":322613938,"number":25748,"title":"Why monorepo?","user":{"login":"artin-phares","id":671082,"avatar_url":"https://avatars2.githubusercontent.com/u/671082?v=4","gravatar_id":"","url":"https://api.github.com/users/artin-phares","html_url":"https://github.com/artin-phares","followers_url":"https://api.github.com/users/artin-phares/followers","following_url":"https://api.github.com/users/artin-phares/following{/other_user}","gists_url":"https://api.github.com/users/artin-phares/gists{/gist_id}","starred_url":"https://api.github.com/users/artin-phares/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/artin-phares/subscriptions","organizations_url":"https://api.github.com/users/artin-phares/orgs","repos_url":"https://api.github.com/users/artin-phares/repos","events_url":"https://api.github.com/users/artin-phares/events{/privacy}","received_events_url":"https://api.github.com/users/artin-phares/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2018-05-13T17:54:38Z","updated_at":"2018-05-21T16:57:10Z","closed_at":null,"author_association":"NONE","body":"1. I want to see .d.ts for `@types/X` package without cloning repo.  \r\nBut when I open types folder on github I see following error, and `X` folder is not listed.  \r\n`Sorry, we had to truncate this directory to 1,000 files. 3,413 entries were omitted from the list.`\r\n\r\n2. I want to see what issues already filed for `@types/X` and file new one.  \r\nBut when I open issues tab I see >2k entries for all the packages... I wonder how contributors even find issues filed for their definitions (or they don't?).\r\n\r\nWhy typings do not live in separate repos? Isn't this monorepo a total mess?"},"comment":{"url":"https://api.github.com/repos/DefinitelyTyped/DefinitelyTyped/issues/comments/390715491","html_url":"https://github.com/DefinitelyTyped/DefinitelyTyped/issues/25748#issuecomment-390715491","issue_url":"https://api.github.com/repos/DefinitelyTyped/DefinitelyTyped/issues/25748","id":390715491,"user":{"login":"artin-phares","id":671082,"avatar_url":"https://avatars2.githubusercontent.com/u/671082?v=4","gravatar_id":"","url":"https://api.github.com/users/artin-phares","html_url":"https://github.com/artin-phares","followers_url":"https://api.github.com/users/artin-phares/followers","following_url":"https://api.github.com/users/artin-phares/following{/other_user}","gists_url":"https://api.github.com/users/artin-phares/gists{/gist_id}","starred_url":"https://api.github.com/users/artin-phares/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/artin-phares/subscriptions","organizations_url":"https://api.github.com/users/artin-phares/orgs","repos_url":"https://api.github.com/users/artin-phares/repos","events_url":"https://api.github.com/users/artin-phares/events{/privacy}","received_events_url":"https://api.github.com/users/artin-phares/received_events","type":"User","site_admin":false},"created_at":"2018-05-21T16:57:10Z","updated_at":"2018-05-21T16:57:10Z","author_association":"NONE","body":"> What problem is splitting up DT into 4,000 separate GitHub repos going to solve?\r\n\r\n1. As a user you reach sources faster. You don't have to use some additional app like TypeSearch to reach sources. On npm you have a link directly to needed typing-repo.\r\n\r\n2. As a user its easier to see current issues and file new one.\r\n    - You don't have to search and filter on one huge repo with >2k issues. What if reporter forgets to follow issue naming rules (ie. `[@types/name-of-package] Issue description`)? You never find needed issues.\r\n    - As such it's less possible to file duplicates.\r\n\r\n3. As a contributor you can clearly monitor how many issues you have in your repository.\r\n    - You don't have to (again) filter anything to get issues for your concrete typing. Less possible to miss needed issues.\r\n    - You have a clear motivation to keep issues number low. Issues number is not shared responsibility anymore.\r\n    - As such it's less possible to have forgotten issues [hanging there for years](https://github.com/DefinitelyTyped/DefinitelyTyped/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc+).\r\nEg. there is 1 issue page from 2013, 5 issue pages from 2014, and so on.\r\n\r\n4. As TypeScript team member you spent more time on improving typescript itself (eg. jsdoc support), instead of maintaining/merging/reviewing thousands of typings for lots of npm packages out there.  \r\nIn mature ecosystem that's what community should do.  \r\n    - > We run repo-wide lint rules that catch common errors\r\n\r\n        Well release lint preset with all the recommended rules, and advise all contributors to use latest version of that preset.\r\n    - > We find and fix definitions with things broken by future compiler versions.\r\n\r\n        That's what community contributors should do. Version of expected ts-compiler should be clearly stated in `peerDependency` section of `package.json` of typing-package, so it warns you when you use it in wrong environment.\r\n\r\n"}}
{"actor":{"display_login":"artin-phares"}}