Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / aleclarson/vite-tsconfig-paths issues and pull requests
#166 - Add test for extending empty include or empty files
Pull Request -
State: open - Opened by jdharrisnz 3 days ago
#165 - option to skip paths
Pull Request -
State: closed - Opened by lsnow99 4 days ago
- 1 comment
#164 - Defining `include` while extending from a tsconfig that has `"files": []` or `"include": []` causes nothing to happen
Issue -
State: open - Opened by jdharrisnz 4 days ago
- 2 comments
#163 - tsconfig paths - cannot resolve self.
Issue -
State: closed - Opened by jackmillward 6 days ago
- 2 comments
#162 - [5.1.1] `vite-tsconfig-paths` stopped understanding my `paths`
Issue -
State: closed - Opened by burtek 7 days ago
- 5 comments
#161 - vite marked as peerDependency but uses direct import from vite
Issue -
State: closed - Opened by MarZab 18 days ago
- 1 comment
#160 - fix: resolve with base url
Pull Request -
State: closed - Opened by himself65 about 2 months ago
#159 - docs: mention allowJs and loose options earlier in readme
Pull Request -
State: closed - Opened by aolyang about 2 months ago
#158 - v5 breaks if you have both tsconfig and jsconfig
Issue -
State: closed - Opened by simon-abbott about 2 months ago
- 1 comment
#157 - fix: tolerate `resolveId` calls with win32-style importer path
Pull Request -
State: closed - Opened by lisonge 2 months ago
#156 - Support for ${configDir} syntax
Issue -
State: closed - Opened by 2LeoCode 2 months ago
- 6 comments
Labels: help wanted
#155 - [ERROR] "vite-tsconfig-paths" resolved to an ESM file. ESM file cannot be loaded by `require`
Issue -
State: closed - Opened by simplenotezy 3 months ago
- 5 comments
Labels: mistaken
#154 - File paths correct for barrel file imports, but not changed for 'nested' path imports (after build)
Issue -
State: closed - Opened by Carnageous 3 months ago
- 2 comments
Labels: mistaken
#153 - Improvements to the test suite
Issue -
State: open - Opened by aleclarson 3 months ago
- 1 comment
Labels: help wanted
#152 - TS can't find package types of `v5`
Issue -
State: closed - Opened by mikestopcontinues 3 months ago
- 2 comments
#152 - TS can't find package types of `v5`
Issue -
State: closed - Opened by mikestopcontinues 3 months ago
- 2 comments
#151 - chore: drop CJS build
Pull Request -
State: closed - Opened by benmccann 3 months ago
#150 - vite-tsconfig-paths cannot import a basic TSconfig extends in sub-folder
Issue -
State: open - Opened by matthew-dean 4 months ago
- 3 comments
Labels: upstream bug
#149 - Vitest v2 (just released) breaks this
Issue -
State: closed - Opened by kevbook 4 months ago
- 1 comment
#148 - Rollup failed to resolve import
Issue -
State: open - Opened by rexkenley 4 months ago
- 3 comments
#147 - Add ability to skip some directories
Issue -
State: closed - Opened by Akiyamka 4 months ago
#146 - feat: add `skip` option
Pull Request -
State: closed - Opened by Akiyamka 4 months ago
- 1 comment
#145 - Vite fails to find `index' files on aliased paths when resolving Web Worker modules
Issue -
State: closed - Opened by haakonjackfloat 5 months ago
- 1 comment
#144 - fix: subpath imports issue
Pull Request -
State: closed - Opened by fcasibu 5 months ago
- 4 comments
Labels: abandoned
#143 - Vite fails to resolve files when vite-tsconfig-paths is used alongside vite-plugin-svgr, but only on Windows
Issue -
State: open - Opened by bladeSk 5 months ago
- 1 comment
Labels: platform: windows
#142 - aliases referenced within vite.config.ts are not recognized
Issue -
State: closed - Opened by basaran 5 months ago
- 2 comments
#142 - aliases referenced within vite.config.ts are not recognized
Issue -
State: open - Opened by basaran 5 months ago
- 1 comment
#141 - How does this work with native ESM package.json subpath imports?
Issue -
State: open - Opened by CMCDragonkai 6 months ago
- 1 comment
#140 - CJS Build warning
Issue -
State: closed - Opened by nicobao 7 months ago
- 2 comments
#139 - fix: upgrade tsconfck to fix bug that could cause a deadlock
Pull Request -
State: closed - Opened by daihere1993 8 months ago
- 1 comment
#138 - Issue with symlinks on macOS
Issue -
State: open - Opened by shellscape 9 months ago
- 3 comments
Labels: bug
#137 - vite silently fails with `[email protected]`
Issue -
State: closed - Opened by LucidityDesign 10 months ago
- 11 comments
Labels: waiting for response
#136 - tsconfck v3.0 require node 18
Issue -
State: closed - Opened by eightHundreds 10 months ago
- 1 comment
#135 - [BUG] "[vite]: Rollup failed to resolve import" with vite-tsconfig-paths plugin
Issue -
State: open - Opened by Giorno-Giovana 10 months ago
- 7 comments
#134 - vite build.rollupOptions break proper path inference
Issue -
State: closed - Opened by nik-webdevelop 10 months ago
- 2 comments
Labels: abandoned
#133 - Full Working Example?
Issue -
State: open - Opened by shellscape 10 months ago
- 4 comments
#132 - Circular reference between tsconfig files leads to deadlock
Issue -
State: closed - Opened by bitschubse 10 months ago
- 9 comments
Labels: help wanted
#131 - 4.3.0: No "exports" main defined
Issue -
State: closed - Opened by echocrow 10 months ago
- 4 comments
#129 - Broken in Vite 5
Issue -
State: closed - Opened by tervay 11 months ago
- 9 comments
Labels: upstream bug
#128 - fix: forward options when calling `this.resolve`
Pull Request -
State: closed - Opened by pcattori 12 months ago
- 2 comments
#127 - Issue with `4.2.1`: Cannot find module 'vite-tsconfig-paths'
Issue -
State: closed - Opened by maoosi 12 months ago
- 1 comment
#126 - Question: Is this intended to also work with `vitest typecheck`?
Issue -
State: closed - Opened by b0o about 1 year ago
- 1 comment
#125 - Does not work using slash as symbol alias
Issue -
State: closed - Opened by elboletaire about 1 year ago
- 1 comment
Labels: duplicate
#124 - Why not simply import tsconfig.json in vite.config.js?
Issue -
State: closed - Opened by jaymakes11 about 1 year ago
- 1 comment
#123 - Can't get the plugin to work with Nuxt and Vitest
Issue -
State: open - Opened by datsenkoboos over 1 year ago
- 7 comments
Labels: help wanted
#123 - Can't get the plugin to work with Nuxt and Vitest
Issue -
State: open - Opened by datsenkoboos over 1 year ago
- 8 comments
Labels: help wanted
#123 - Can't get the plugin to work with Nuxt and Vitest
Issue -
State: open - Opened by datsenkoboos over 1 year ago
- 9 comments
Labels: help wanted
#122 - Type 'Plugin_2' is not assignable to type 'PluginOption'.
Issue -
State: closed - Opened by dardino over 1 year ago
- 1 comment
Labels: mistaken
#122 - Type 'Plugin_2' is not assignable to type 'PluginOption'.
Issue -
State: closed - Opened by dardino over 1 year ago
- 1 comment
Labels: mistaken
#121 - Paths are not getting changed at all
Issue -
State: closed - Opened by ncls-alien over 1 year ago
- 14 comments
Labels: platform: windows, plugin: electron
#121 - Paths are not getting changed at all
Issue -
State: open - Opened by ncls-alien over 1 year ago
- 11 comments
Labels: platform: windows, plugin: electron
#121 - Paths are not getting changed at all
Issue -
State: open - Opened by ncls-alien over 1 year ago
- 10 comments
Labels: platform: windows, plugin: electron
#120 - Tests file absolute paths are not being picked up
Issue -
State: closed - Opened by eamonnprwalsh over 1 year ago
- 1 comment
Labels: mistaken
#120 - Tests file absolute paths are not being picked up
Issue -
State: closed - Opened by eamonnprwalsh over 1 year ago
- 1 comment
Labels: mistaken
#120 - Tests file absolute paths are not being picked up
Issue -
State: closed - Opened by eamonnprwalsh over 1 year ago
- 1 comment
Labels: mistaken
#119 - feat(perf): leverage tsconfk caching to skip redundant work
Pull Request -
State: closed - Opened by fwouts over 1 year ago
- 2 comments
#119 - Leverage tsconfk caching to skip redundant work
Pull Request -
State: open - Opened by fwouts over 1 year ago
#119 - Leverage tsconfk caching to skip redundant work
Pull Request -
State: open - Opened by fwouts over 1 year ago
#118 - Proposal: lazy loading approach to speed up `configResolved` hook
Issue -
State: open - Opened by fwouts over 1 year ago
- 2 comments
#118 - Proposal: lazy loading approach to speed up `configResolved` hook
Issue -
State: closed - Opened by fwouts over 1 year ago
- 4 comments
#118 - Proposal: lazy loading approach to speed up `configResolved` hook
Issue -
State: open - Opened by fwouts over 1 year ago
- 1 comment
#117 - aliases not working on declaration files in dist/
Issue -
State: closed - Opened by chirastefan over 1 year ago
- 3 comments
#117 - aliases not working on declaration files in dist/
Issue -
State: closed - Opened by chirastefan over 1 year ago
- 3 comments
#117 - aliases not working on declaration files in dist/
Issue -
State: closed - Opened by chirastefan over 1 year ago
- 3 comments
#116 - Use `resolve.alias` to support `.scss` import resolution
Issue -
State: closed - Opened by matthew-dean over 1 year ago
- 5 comments
Labels: enhancement, wontfix
#116 - Use `resolve.alias` to support `.scss` import resolution
Issue -
State: closed - Opened by matthew-dean over 1 year ago
- 4 comments
Labels: enhancement, wontfix
#116 - Use `resolve.alias` to support `.scss` import resolution
Issue -
State: closed - Opened by matthew-dean over 1 year ago
- 4 comments
Labels: enhancement, wontfix
#115 - Use wrong tsconfig when exists multiple tsconfig files
Issue -
State: closed - Opened by Singloo over 1 year ago
- 6 comments
Labels: abandoned
#115 - Use wrong tsconfig when exists multiple tsconfig files
Issue -
State: closed - Opened by Singloo over 1 year ago
- 6 comments
Labels: abandoned
#115 - Use wrong tsconfig when exists multiple tsconfig files
Issue -
State: closed - Opened by Singloo over 1 year ago
- 6 comments
Labels: abandoned
#114 - Failed to resolve import
Issue -
State: open - Opened by f1am3d over 1 year ago
- 6 comments
#114 - Failed to resolve import
Issue -
State: open - Opened by f1am3d over 1 year ago
- 6 comments
#114 - Failed to resolve import
Issue -
State: closed - Opened by f1am3d over 1 year ago
- 6 comments
Labels: abandoned
#113 - Error: The following dependencies are imported but could not be resolved:
Issue -
State: closed - Opened by kasir-barati over 1 year ago
- 7 comments
#112 - What happens when alias is identical to node_modules package name?
Issue -
State: open - Opened by caldwell-63 over 1 year ago
- 1 comment
#111 - Is "*" in path resolver supported?
Issue -
State: closed - Opened by crhistianramirez over 1 year ago
- 5 comments
Labels: mistaken
#110 - Compatability with Vite 4.3.x?
Issue -
State: closed - Opened by jafin over 1 year ago
- 5 comments
Labels: wontfix, upstream bug
#109 - feat: add `ignoreConfigErrors` option
Pull Request -
State: closed - Opened by jgoux over 1 year ago
- 1 comment
#108 - fix: check for undefined "compilerOptions" property
Pull Request -
State: closed - Opened by igordreher over 1 year ago
- 1 comment
#107 - Monorepo crash parsing unused sibling tsconfig.json
Issue -
State: closed - Opened by IlyaSemenov over 1 year ago
- 4 comments
Labels: bug, help wanted
#106 - Remove global dependency on Yarn in development scripts
Issue -
State: open - Opened by aleclarson over 1 year ago
Labels: help wanted
#105 - TypeScript types doesn't seem to be compatible in `vite.config.ts` with `defineConfig()` API
Issue -
State: closed - Opened by caldwell-63 over 1 year ago
- 3 comments
#104 - chore: upgrade tsconfck to 2.1.0
Pull Request -
State: closed - Opened by christopherschroer over 1 year ago
- 5 comments
#103 - Enable Typescript 5.0 compatiblity
Issue -
State: closed - Opened by christopherschroer over 1 year ago
- 1 comment
Labels: help wanted
#102 - [plugin externalize-deps] Missing "./dist" specifier in "vite-tsconfig-paths" package
Issue -
State: closed - Opened by quantuminformation over 1 year ago
- 3 comments
#101 - Why are absolute ids skipped?
Issue -
State: open - Opened by eddiemonge over 1 year ago
- 4 comments
Labels: bug, help wanted
#100 - fix(yarn-pnp): make vite an optional peer dep
Pull Request -
State: closed - Opened by DiFuks over 1 year ago
#99 - Path options do not work with `vitest` `vi.mock`
Issue -
State: closed - Opened by haakonjackfloat almost 2 years ago
- 5 comments
#98 - Error [ERR_MODULE_NOT_FOUND] in slightly modified demo when using tsconfig path alias
Issue -
State: closed - Opened by wvhulle almost 2 years ago
- 1 comment
#97 - feat: ignore missing tsconfig
Pull Request -
State: closed - Opened by haikyuu almost 2 years ago
- 1 comment
#96 - Enhancement: Add option to silently fail if no ts config file is found
Issue -
State: closed - Opened by haikyuu almost 2 years ago
#95 - Releases not updating
Issue -
State: closed - Opened by eddiemonge almost 2 years ago
- 1 comment
#94 - Usage with yarn pnp
Issue -
State: closed - Opened by eyeball-bot almost 2 years ago
- 6 comments
#93 - v4 fails if tsconfig exists, but does not contain compilerOptions
Issue -
State: closed - Opened by simon-abbott almost 2 years ago
- 1 comment
Labels: help wanted
#92 - I think there's a conflict with plug-in `@rollup/plugin-node-resolve`
Issue -
State: closed - Opened by jjunyjjuny almost 2 years ago
- 1 comment
#91 - chore: remove `peerDependencies` from `package.json`
Pull Request -
State: closed - Opened by wadefletch almost 2 years ago
- 1 comment
#90 - Incompatibility with vitest 0.25.6
Issue -
State: closed - Opened by harveylee almost 2 years ago
- 1 comment
Labels: wontfix
#89 - Peer dependency warning when installed alongside Vitest.
Issue -
State: closed - Opened by wadefletch almost 2 years ago
- 3 comments
#88 - Minor: warning [email protected]: The engine "pnpm" appears to be invalid.
Issue -
State: closed - Opened by ehahn9 almost 2 years ago
- 1 comment
Labels: upstream bug
#87 - v4 fails on resolving common libraries outside root
Issue -
State: open - Opened by janakg almost 2 years ago
- 16 comments
Labels: help wanted