-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Changing the file extension from .ts to .js #478
Comments
as per the README.md, the maintainer provided with this link https://github.com/krishnaacharyaa/wanderlust/blob/main/.github/CONTRIBUTING.md#setting-up-the-project that has a package.json with npm run installer script defined in it to handle both frontend & backend but after executing this command vite is not recognized in frontend and requires npm i --legacy-peer-deps to get that issue resolved then npm run dev runs the frontend successfully. The backend needs DB Compass with the import of dummy data provided in the backend data folder and redis running in local machine. As DB and Redis are called while running server. To run backend, I first installed ts-node and typescript as backend has .ts file but scripts in package.json of backend needs server.js which is not there. npm start can not directly run the .js file. I compiled .ts to .js by npx tsc command than I changed package.json, and modified start script to "node dist/server.js" this started the server. Redis and DB compass with wanderlust db > posts collection > sample_posts.json import are required* Also Google Client id needs to be set in backend .env (in backend run cp .env.sample .env). This can be random. |
Is there an existing issue for this?
Current Behavior
Currently all the files are having .ts extension but they have been imported with .js extension, because of this the system is unable to fetch the required file due to mismatch of the file names.
Expected Behavior
The extension of the file name and the imported files should be same.
Reproduction steps
Screenshots
Logs
Browsers
No response
OS
Linux
The text was updated successfully, but these errors were encountered: