tsdocs.dev helps you browse reference typescript documentation for any package or version of a library. Made with the help of typedoc
TS Docs | Reference docs for npm packages
tsdocs.dev helps you browse reference typescript documentation for any package or version of a library. Made with the help of typedoc
A Proposal For Module Resolution · Issue #50152 · microsoft/TypeScript
Background When a user writes a module specifier (the string literal after from in an import declaration) in a TypeScript file, how should the compiler resolve that string to a file on disk to be included in type checking? Because TypeScript never rewrites module specifiers in its JavaScript emit, the only possible answer is that it should mirror whatever resolution behavior the code’s intended ru
You may not need a bundler for your NPM library
I have seen a couple threads on twitter where people complain about the difficulty with publishing NPM libraries or ask what starter kit they should use (or, people recommended starter packs anyways) Example threads https://twitter.com/cramforce/status/1513903035197526017 https://twitter.com/oleg008/status/1510006191296061441 https://twitter.com/iansu/status/1524860613943382017 https://twitter.com
Denoからnpmパッケージを使用するノウハウ
このページの内容は古くなっています。 最新の情報については、以下のページを参照いただければと思います。 https://zenn.dev/uki00a/books/effective-deno/viewer/how-to-use-npm-packages DenoはJavaScript/TypeScriptランタイムであるため、既存のNode.jsやブラウザの資産をある程度活かすことができます。 この記事では、Denoからnpmパッケージを使用する際のノウハウについて、パッケージの種別ごとに解説します。 DenoとNode.jsの両方をサポートするパッケージ Node.jsとブラウザの両方で動作するパッケージ CommonJS形式で配布されているパッケージ Node.jsのAPIに依存するパッケージ DenoとNode.jsの両方をサポートするパッケージ npmパッケージの中にはDenoと
GitHub - jaredpalmer/tsdx: Zero-config CLI for TypeScript package development
Despite all the recent hype, setting up a new TypeScript (x React) library can be tough. Between Rollup, Jest, tsconfig, Yarn resolutions, ESLint, and getting VSCode to play nicely....there is just a whole lot of stuff to do (and things to screw up). TSDX is a zero-config CLI that helps you develop, test, and publish modern TypeScript packages with ease--so you can focus on your awesome new librar
Publishing Typings to DefinitelyTyped
IntroTypescript is a great addition to JavaScript. Unfortunately, not every JS package has definitions for TypeScript. Of course, you could create your custom definition in your project, but I believe that sharing these definitions makes things easier for the community: A large community maintains shared typingsThe review process could provide valuable insightsThe definition helps spread the Types
Writing a Node.js module in TypeScript
One of the best things about Node.js is its massive module ecosystem. With bundlers like webpack we can leverage these even in the browser outside of Node.js. Let’s look at how we can build a module with TypeScript usable by both JavaScript developers and TypeScript developers. Before we get started make sure that you have Node.js installed – you should ideally have a version of 6.11 or higher. Ad
Untyped Imports in TypeScript
February 17, 2017TypeScript 2.1 makes it a lot easier to work with untyped imports. Previously, the compiler was overly strict and would give you an error when you imported a module that doesn't ship with type definitions: Starting with TypeScript 2.1, the compiler will no longer complain if there are no type declarations for a module. TypeScript is happy with untyped modules and your editor doesn
The Future of Declaration Files - TypeScript
Declaration files (.d.ts files) are a fundamental part of using existing JavaScript libraries in TypeScript, but getting them has always been a place where we’ve known there was room for improvement. As we get closer to TypeScript 2.0, we’re very excited to show off a sneak peak of our plan to simplify things. Getting type declarations in TypeScript 2.0 will require no tools apart from npm. As an
State of Type Script Packages | Angular Class
As a module author and developer, I love TypeScript. It allows me to write, publish and consume 100% type-safe JavaScript. Features like autocompletion, type validation and ES6 features are now part of my typical workflow. I’ve published half a dozen modules on NPM, but no one has ever been able to consume the type definitions from them. Why’s that? Let’s quickly take a step back. TypeScript inclu
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - arethetypeswrong/arethetypeswrong.github.io: Tool for analyzing TypeScript types of npm packages
monorepo-utils/packages/@monorepo-utils/workspaces-to-typescript-project-references at master · azu/monorepo-utils
Publish `@types` Packages to the GitHub Registry · Issue #33330 · microsoft/TypeScript
GitHub - 8th713/npm-package-support: UserScript that detects TypeScript support of npm package.
GitHub - jeffijoe/typesync: Install missing TypeScript typings for dependencies in your package.json.
GitHub - nfour/types-installer: Installs @types for your dependencies
GitHub - xavdid/typed-install: Easily install new packages and their types, every time.
GitHub - mizchi/trans-loader: webpack-less frontend with service-worker
Duplicate type declarations with npm link · Issue #6496 · microsoft/TypeScript
GitHub - microsoft/types-publisher: This repo has moved:
