import issues
Closed this issue · 5 comments
Describe the bug
when running the program locally. every time you connect the terminal gets flooded with messages. This also presumably causes the app to give an error every time it hot reloads
info - ready on http://localhost:3000
event - build page: /
wait - compiling...
warn - ./pages/index.js
Should not import the named export 'name' (imported as 'name') from default-exporting module (only default export is available soon)
./src/About.js
Should not import the named export 'about'.'social'.'length' (imported as 'about') from default-exporting module (only default export is available soon)
./src/About.js
Should not import the named export 'about'.'social'.'map' (imported as 'about') from default-exporting module (only default export is available soon)
./src/About.js
Should not import the named export 'about'.'description' (imported as 'about') from default-exporting module (only default export is available soon)
./src/About.js
Should not import the named export 'about'.'picture' (imported as 'about') from default-exporting module (only default export is available soon)
./src/Experience.js
Should not import the named export 'experience' (imported as 'experience') from default-exporting module (only default export is available soon)
./src/Experience.js
Should not import the named export 'experience' (imported as 'experience') from default-exporting module (only default export is available soon)
./src/Landing.js
Should not import the named export 'landing'.'professionalDetails'.'map' (imported as 'landing') from default-exporting module (only default export is available soon)
./src/Landing.js
Should not import the named export 'landing'.'title' (imported as 'landing') from default-exporting module (only default export is available soon)
./src/Landing.js
Should not import the named export 'landing'.'subtitles' (imported as 'landing') from default-exporting module (only default export is available soon)
./src/Skills.js
Should not import the named export 'skills' (imported as 'skills') from default-exporting module (only default export is available soon)
./src/Skills.js
Should not import the named export 'skills' (imported as 'skills') from default-exporting module (only default export is available soon)
To Reproduce
Steps to reproduce the behavior:
- Connect to your localhost with the browser after running
yarn && yarn dev
Hello again.
I wasn't able to reproduce these warnings. However, I looked them up, and it seems like these have something to do with webpack and importing from json files. Maybe this is being caused by the parts of data.json that are being imported in different files. Anyway, it would be great if you could send the hot-reload error you mentioned in the issues as well.
Thanks
sorry for the late response. here is the error code you are asking about. It always shows up for 1-2 sec and then the site reloads itself again and then its fine again.
also in the console there comes an error
Solved the "text content did not match" SSR issue in #12 and the "Hot-reload" issue in #13. Feel free to close these issues if this worked out for you.
#11 showed up for me in Vercel's build logs post-deployment. Storing this data in a js object instead of a json file could work. It'll also increase the customizability of the theme object, since we'll be able to pass functions as well. But I'm not sure if this is the best way to solve this problem. What do you think @timmermansjoy?
from what I have seen is this the issue. It worked for when I did it in skills.js but not for the rest and I didnt look further