Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / axe-me/vite-plugin-node issues and pull requests
#114 - After Upgrading from 3.1.0 to 4.0.0, can‘t bunddle output ESM
Issue -
State: closed - Opened by xiaofuyesnew about 1 month ago
- 2 comments
#113 - chore: upgrade dependencies / migrate to ESM
Pull Request -
State: open - Opened by dirkluijk about 2 months ago
- 2 comments
#112 - feat: add support for Vite 5
Pull Request -
State: open - Opened by dirkluijk about 2 months ago
- 2 comments
#111 - Not working for Nestjs with socket
Issue -
State: open - Opened by Jedliu 6 months ago
- 1 comment
#111 - Not working for Nestjs with socket
Issue -
State: open - Opened by Jedliu 6 months ago
- 1 comment
#110 - HMR reloads from root - app.ts
Issue -
State: open - Opened by jazelly 7 months ago
#109 - Expose viteNodeApp after async operations
Issue -
State: closed - Opened by jazelly 7 months ago
- 2 comments
#108 - Nest middleware not receiving express Request
Issue -
State: open - Opened by judocode 8 months ago
#107 - Fix typo in README
Pull Request -
State: open - Opened by ytsunekawa 8 months ago
#105 - not support parameter decorators
Issue -
State: open - Opened by jkhuangfu 10 months ago
- 5 comments
#103 - Add support for Vite 5
Issue -
State: closed - Opened by metalmarker 12 months ago
- 13 comments
#102 - HMR only works after the application web page is reloaded
Issue -
State: open - Opened by PurpleTape 12 months ago
- 2 comments
#101 - Nest.js + Fastify: No driver (HTTP) has been selected.
Issue -
State: closed - Opened by simplenotezy about 1 year ago
- 2 comments
#100 - fix: [GH-99] Explicitly import http types
Pull Request -
State: closed - Opened by HishamAli81 about 1 year ago
#99 - Module '"http"' has no default export.
Issue -
State: closed - Opened by HishamAli81 about 1 year ago
- 2 comments
#98 - I used the nestjs and vite-plugin-node example, they threw this err,,,what makes it so
Issue -
State: closed - Opened by DankeBIBI about 1 year ago
- 2 comments
#97 - NestJs Build error - Failed to resolve entry for package "fs"
Issue -
State: open - Opened by marviobezerra over 1 year ago
#96 - HMR doesn't work
Issue -
State: closed - Opened by lubiah over 1 year ago
- 3 comments
#95 - How to render some routes using Nest and some using Vite?
Issue -
State: open - Opened by thgh over 1 year ago
- 1 comment
#94 - `vite-plugin-node` vs `vite-node`
Issue -
State: closed - Opened by Jazcash over 1 year ago
- 2 comments
#93 - server example
Issue -
State: closed - Opened by Jacknq over 1 year ago
- 1 comment
#92 - Configuring https server results in an exception
Issue -
State: open - Opened by metalmarker over 1 year ago
- 5 comments
#91 - HMR not working, server going through a full reload every time a file changes
Issue -
State: open - Opened by pthieu over 1 year ago
#90 - `vite build` does not bundle the dependencies
Issue -
State: closed - Opened by tresabhi over 1 year ago
- 6 comments
#89 - Can it bundle into a single file?
Issue -
State: open - Opened by TheLucifurry over 1 year ago
#88 - NestJS example not working
Issue -
State: open - Opened by RickStanley over 1 year ago
- 3 comments
#87 - Proposal: Simpler way to bundle Node apps with Vite
Issue -
State: open - Opened by srmagura over 1 year ago
- 3 comments
#86 - Add an option to automatically load modules when the server is ready
Pull Request -
State: closed - Opened by xmuller over 1 year ago
- 1 comment
#85 - Node Server doesn't start automatically
Issue -
State: closed - Opened by kefniark over 1 year ago
- 7 comments
#84 - feat: SwcFileChangeToLogMessage vite-plugin-node #46
Pull Request -
State: open - Opened by SymphonyIceAttack over 1 year ago
- 1 comment
#83 - Provider a way to solve the problem which import.meta.env Not found
Issue -
State: open - Opened by SymphonyIceAttack over 1 year ago
#82 - support for import.meta.hot ?
Issue -
State: open - Opened by wighawag over 1 year ago
#81 - add rimraf as dev deps + fix README.md spelling
Pull Request -
State: closed - Opened by wighawag over 1 year ago
#80 - How to handle the migration folder with vite config
Issue -
State: open - Opened by mtt-artis over 1 year ago
#79 - h3 support?
Issue -
State: open - Opened by lautiamkok over 1 year ago
- 1 comment
#78 - can not generate sourcemap
Issue -
State: closed - Opened by ianzone over 1 year ago
#77 - vite ssr import 2 is not a function
Issue -
State: open - Opened by tomdavidson over 1 year ago
- 1 comment
#75 - Debug example
Issue -
State: open - Opened by Jacknq almost 2 years ago
- 4 comments
#74 - ReferenceError
Issue -
State: closed - Opened by Jacknq almost 2 years ago
- 1 comment
#73 - setInterval not cleared
Issue -
State: open - Opened by vlastoun almost 2 years ago
#72 - SSR build not work
Issue -
State: open - Opened by Farnsi almost 2 years ago
- 3 comments
#71 - NestJS, SocketIO not working
Issue -
State: closed - Opened by angelhdzmultimedia almost 2 years ago
- 3 comments
#70 - It disrupts the static serving of Vite
Issue -
State: open - Opened by branaway almost 2 years ago
- 1 comment
#69 - Support for Apollo Server?
Issue -
State: closed - Opened by lautiamkok almost 2 years ago
- 3 comments
#68 - Update to Vite 4.0.3 / Async config support
Pull Request -
State: closed - Opened by Filyus almost 2 years ago
- 2 comments
#67 - Check if the Nest app is initialized
Pull Request -
State: closed - Opened by Filyus almost 2 years ago
#66 - Check if the Nest app is already initialized
Pull Request -
State: closed - Opened by Filyus almost 2 years ago
#65 - NestJS read properties of undefined when tsCompiler is esbuild
Issue -
State: closed - Opened by railsstudent almost 2 years ago
- 2 comments
#64 - feat: add support for fastify in nest
Pull Request -
State: closed - Opened by imranbarbhuiya about 2 years ago
- 1 comment
#63 - Add vite 3 as a peer dependency
Pull Request -
State: closed - Opened by janza about 2 years ago
- 1 comment
#62 - HMR does not seem to work
Issue -
State: closed - Opened by FluffyDiscord about 2 years ago
- 3 comments
#61 - TypeORM? Is it possible?
Issue -
State: closed - Opened by OskarLebuda about 2 years ago
- 1 comment
#60 - Is it possible to pass your own CLI commands to boot up the server?
Issue -
State: closed - Opened by jaequery about 2 years ago
- 1 comment
#59 - Do you plan to support Vite 3.0?
Issue -
State: closed - Opened by shuuuuun over 2 years ago
- 6 comments
#58 - with graphql + nestjs, vite seems to be adding to the schema on every request causing "Schema must contain uniquely named types" -- repository provided
Issue -
State: closed - Opened by sebastiangug over 2 years ago
- 1 comment
#57 - Vite-plugin-ssr support
Issue -
State: closed - Opened by stychu over 2 years ago
- 2 comments
#56 - allow to use with typescript(ttypescript) as a compiler
Issue -
State: open - Opened by capaj over 2 years ago
#55 - [ERROR] HMR not working
Issue -
State: closed - Opened by angelhdzmultimedia over 2 years ago
- 6 comments
#54 - ReferenceError: fetch is not defined
Issue -
State: closed - Opened by Archsx over 2 years ago
- 4 comments
#53 - import.meta.hot.dispose not working?
Issue -
State: closed - Opened by schummar over 2 years ago
- 2 comments
#52 - Does not work with @nestjs/graphql
Issue -
State: closed - Opened by stevefan1999-personal over 2 years ago
- 3 comments
#51 - Publish README.md to GitHub
Issue -
State: closed - Opened by yuchenshi over 2 years ago
- 1 comment
#50 - NestApplication reloading after each GET request
Issue -
State: closed - Opened by vic1707 over 2 years ago
- 6 comments
#49 - Using top level await: Module format cjs does not support top-level await. Use the "es" or "system" output formats rather.
Issue -
State: closed - Opened by juliushuck over 2 years ago
- 2 comments
#48 - Errors with export in `browser-external:...`
Issue -
State: closed - Opened by kasbah over 2 years ago
- 4 comments
#47 - Using this as part of a full stack dev server
Issue -
State: closed - Opened by noam-honig over 2 years ago
- 4 comments
#46 - swc tsCompiler does not seem to do anything
Issue -
State: closed - Opened by EdwardKerckhof over 2 years ago
- 4 comments
#45 - [ERROR] Error That Doesn't Affect Compilation
Issue -
State: closed - Opened by angelhdzmultimedia over 2 years ago
- 2 comments
#44 - how to pass node flag to node?
Issue -
State: closed - Opened by skimhugo over 2 years ago
- 4 comments
#43 - Using vite plugin node for svelte kit
Pull Request -
State: closed - Opened by DarwinSenior over 2 years ago
- 2 comments
#42 - Multiple entry points
Issue -
State: closed - Opened by sebastian0x62 over 2 years ago
- 2 comments
#41 - Express: SSE not working
Issue -
State: closed - Opened by x7airworker over 2 years ago
#40 - Repo example for express cannot find module '@swc/core'
Issue -
State: closed - Opened by gtarsia over 2 years ago
- 1 comment
#39 - Using with standard node server?
Issue -
State: closed - Opened by lucas-jones over 2 years ago
- 3 comments
#38 - NestJS: vite command not working
Issue -
State: closed - Opened by Floppy012 over 2 years ago
- 3 comments
#37 - Error when evaluating SSR module (mongoose dependency)
Issue -
State: closed - Opened by a-ski over 2 years ago
- 3 comments
#36 - peerDependency @swc/core isn't optional
Issue -
State: closed - Opened by JiPaix over 2 years ago
- 2 comments
#35 - Use vite-plugin-node along with @vitejs/plugin-react
Issue -
State: open - Opened by subodhpareek18 over 2 years ago
- 6 comments
#34 - [0.0.18] Cannot find module '@swc/core'
Issue -
State: closed - Opened by JiPaix over 2 years ago
- 2 comments
#33 - Running vite: Cannot modify fastify route without crashing.
Issue -
State: open - Opened by skogs-pa over 2 years ago
- 3 comments
#32 - Move @swc/core to an optional peer dependency
Pull Request -
State: closed - Opened by RDIL over 2 years ago
- 2 comments
#31 - Runtime log are not displayed by vite
Issue -
State: closed - Opened by Tchoupinax over 2 years ago
- 2 comments
#30 - Any NestJS + Fastify example please
Issue -
State: closed - Opened by alexkharech over 2 years ago
- 3 comments
#29 - (proposal): consider using unplugin-swc
Issue -
State: closed - Opened by wight554 over 2 years ago
- 2 comments
#28 - Configuring this package in a NestJS Monorepo
Issue -
State: closed - Opened by oliverabclabs almost 3 years ago
- 2 comments
#27 - Added Marble.js adapter
Pull Request -
State: closed - Opened by enricosecondulfo almost 3 years ago
- 2 comments
#26 - pass dev-Server to Handler
Pull Request -
State: closed - Opened by N0tExisting almost 3 years ago
- 1 comment
#25 - how to extra config to app
Issue -
State: closed - Opened by wangfengyuan almost 3 years ago
- 3 comments
#24 - NestJS + TypeORM support
Issue -
State: closed - Opened by richard-viney almost 3 years ago
- 4 comments
#23 - Node12 support
Issue -
State: closed - Opened by beefancohen about 3 years ago
- 6 comments
#22 - Websockets do not work
Issue -
State: open - Opened by chanced about 3 years ago
- 16 comments
#21 - How to add typescript typecheck?
Issue -
State: closed - Opened by Wharley01 about 3 years ago
- 2 comments
#20 - Build for production?
Issue -
State: closed - Opened by onekiloparsec about 3 years ago
- 8 comments
#19 - feat(deps): ✨ Updating the deps to latest version
Pull Request -
State: closed - Opened by spa5k about 3 years ago
- 1 comment
#18 - Limitation to develop koa2 project
Issue -
State: closed - Opened by percy507 about 3 years ago
- 2 comments
#17 - feat: transform `import.meta.url` as nodejs does
Pull Request -
State: closed - Opened by percy507 about 3 years ago
- 2 comments
#16 - `import.meta.url` returns relative path or wrong absolute path
Issue -
State: closed - Opened by percy507 about 3 years ago
#15 - Can't access my .env file value in app.ts
Issue -
State: closed - Opened by jcc1997 about 3 years ago
- 1 comment
#14 - Request for example working with Docker/docker-compose
Issue -
State: closed - Opened by jgod about 3 years ago
- 2 comments
#13 - __dirname is not defined
Issue -
State: closed - Opened by HexaField about 3 years ago
- 1 comment