You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just installed the package and took the code from the example and I get such errors. The library uses a strange path. I believe, the better way for fix issue is update path in library.
This is not a duplicated issue
I have searched existing issues to ensure this bug has not already been reported
The text was updated successfully, but these errors were encountered:
alTach
changed the title
import error when start
Strange path in package, therefore import error when start
May 12, 2024
alTach
changed the title
Strange path in package, therefore import error when start
Strange path in package @/xx, therefore import error when start
May 12, 2024
Routes
Full routes
Related documentation
https://docs.rsshub.app/guide/
What is expected?
Expected that app is started without error.
What is actually happening?
`
[2:19:08 PM] Starting compilation in watch mode...
node_modules/rsshub/lib/pkg.ts:1:27 - error TS2307: Cannot find module '@/config' or its corresponding type declarations.
1 import { setConfig } from '@/config';
~~~~~~~~~~
node_modules/rsshub/lib/pkg.ts:15:25 - error TS2307: Cannot find module '@/app' or its corresponding type declarations.
15 app = (await import('@/app')).default;
~~~~~~~
src/app.service.ts:6:8 - error TS1192: Module '"/rss_tes_tapp/node_modules/rsshub/lib/pkg"' has no default export.
6 import RSSHub from 'rsshub';
~~~~~~
[2:19:22 PM] Found 3 errors. Watching for file changes.
`
Deployment information
RSSHub demo (https://rsshub.app)
Deployment information (for self-hosted)
No response
Additional info
"rsshub": "^1.0.0-master.5e8ea80"
I just installed the package and took the code from the example and I get such errors. The library uses a strange path. I believe, the better way for fix issue is update path in library.
This is not a duplicated issue
The text was updated successfully, but these errors were encountered: