vite-tsconfig-paths
DefinitelyTyped
vite-tsconfig-paths | DefinitelyTyped | |
---|---|---|
5 | 158 | |
1,183 | 47,254 | |
- | 0.8% | |
6.5 | 10.0 | |
2 months ago | 3 days ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vite-tsconfig-paths
-
From webpack to vite: custom module resolution, sass import, babel config
Following suggestion in the issue, i looked at vite-tsconfig-paths which is even better because i already have configured vscode through typescript config:
-
Trying Vite for team's new front end project, can't seem to configure a base import path?
Try this one. https://github.com/aleclarson/vite-tsconfig-paths
-
Migrating from Create React App (CRA) to Vite
We need vite-tsconfig-paths in order to tell Vite how to resolve absolute paths from the tsconfig file. This way you can import modules like this:
-
Vite: Import path alias only setting tsconfig.json
You can use vite-tsconfig-paths on SvelteKit project. And it doesn't work, plese try delete generated folder for dev server like .svelte-kit.
-
Using Vite with React
We already have configured path aliases with webpack and tsconfig - so I wanted to keep that behavior. Luckily we have the vite-tsconfig-paths exactly for that. It worked well. I could also try using the alias for that.
DefinitelyTyped
-
⚛️ Explaining React's Types
Prior to React 18, it used to include an implicit children prop, making it suitable for components expected to have children. For a long time, though, the implicit children prop type has been removed according to React 18's type changes.
-
Introduction to TypeScript — What is TypeScript?
Additionally, because TypeScript has a well established and widely used install-base, there are already many different definition files in the wild for supporting non-TypeScript supporting projects. One of the more extensive collections of these typings lives at the DefinitelyTyped repository, which publishes the package's community typings under the package names @types/your-package-name (where your-package-name is the name of the project you're looking for typings of) that you can look for on your package manager.
-
5 Resources Each TypeScript Developer Should Know About
View on GitHub
- DefinitelyTyped
-
Show HN: OpenAPI DevTools – Chrome ext. that generates an API spec as you browse
Firefox maintain a library for unified extension API https://github.com/mozilla/webextension-polyfill
Their type definition for HAR request isn't exported https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast...
-
Typescript - Union types e type guards
type NumberOrString = number | string; type Status = "idle" | "loading" | "success" | "failure" // React useState, can receive a value or a function as parameter to serve as initial value. // https://github.com/DefinitelyTyped/DefinitelyTyped/blob/a03856975a17eba524739676affbf70ac4078176/types/react/v17/index.d.ts#L920 function useState(initialState: S | (() => S)): [S, Dispatch>];
- If you ever get called out for using long type names, remember this exists
-
Declaring JSX types in TypeScript 5.1
The TypeScript pull request was merged, so Sebastian (who helps maintain the React type definitions) exercised new powers in this pull request to the DefinitelyTyped repository for the React type definitions. At the time of writing, this pull request is still open, but once merged and shipped the React community we will feel its benefits.
-
DO_NOT_USE_OR_YOU_WILL_BE_FIRED_EXPERIMENTAL_REACT_NODES[keyof DO_NOT_USE_OR_YOU_WILL_BE_FIRED_EXPERIMENTAL_REACT_NODES]
there is an open issue: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/61616
-
Announcing TypeScript 5.1
Relatively infrequently. Normally, if an npm package is popular and doesn’t have its own types, there will be a community provided types declaration file available from https://github.com/DefinitelyTyped/DefinitelyTyped
What are some alternatives?
awesome-vite - ⚡️ A curated list of awesome things related to Vite.js
tsyringe - Lightweight dependency injection container for JavaScript/TypeScript
tsconfig-paths-webpack-plugin - Load modules according to tsconfig paths in webpack.
supabase-js - An isomorphic Javascript client for Supabase. Query your Supabase database, subscribe to realtime events, upload and download files, browse typescript examples, invoke postgres functions via rpc, invoke supabase edge functions, query pgvector.
Snowpack - ESM-powered frontend build tool. Instant, lightweight, unbundled development. ✌️ [Moved to: https://github.com/FredKSchott/snowpack]
typegoose - Typegoose - Define Mongoose models using TypeScript classes.
rollup-plugin-visualizer - 📈⚖️ Visuallize your bundle
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
esbuild - An extremely fast bundler for the web
bpmn-visualization-js - A TypeScript library for visualizing process execution data on BPMN diagrams
webpack-bundle-analyzer - Webpack plugin and CLI utility that represents bundle content as convenient interactive zoomable treemap
middy - 🛵 The stylish Node.js middleware engine for AWS Lambda 🛵