Error after building layer5 locally using wsl2

ERROR #98124 WEBPACK

Generating development SSR bundle failed

Can’t resolve ‘react-is’ in ‘C:\TempSavio\Projects\Opensource\layer5\node_modules\styled-components\dist’

If you’re trying to use a package make sure that ‘react-is’ is installed. If you’re trying to use a local file make sure
that the path is correct.

File: node_modules\styled-components\dist\styled-components.esm.js:1:0

warn ./node_modules/react-accessible-accordion/dist/es/index.js
Attempted import error: ‘useId’ is not exported from ‘react’ (imported as ‘useId’).

ERROR #98124 WEBPACK

Generating development JavaScript bundle failed

Can’t resolve ‘react-is’ in ‘C:\TempSavio\Projects\Opensource\layer5\node_modules\styled-components\dist’

If you’re trying to use a package make sure that ‘react-is’ is installed. If you’re trying to use a local file make sure
that the path is correct.

File: node_modules\styled-components\dist\styled-components.browser.esm.js:1:0

ERROR #98124 WEBPACK

Generating development JavaScript bundle failed

Can’t resolve ‘@fullcalendar/core/index.js’ in
‘C:\TempSavio\Projects\Opensource\layer5\node_modules@fullcalendar\google-calendar’

If you’re trying to use a package make sure that ‘@fullcalendar/core/index.js’ is installed. If you’re trying to use a
local file make sure that the path is correct.

File: node_modules@fullcalendar\google-calendar\index.js:1:0

ERROR #98124 WEBPACK

Generating development JavaScript bundle failed

Can’t resolve ‘@fullcalendar/core/internal.js’ in
‘C:\TempSavio\Projects\Opensource\layer5\node_modules@fullcalendar\google-calendar’

If you’re trying to use a package make sure that ‘@fullcalendar/core/internal.js’ is installed. If you’re trying to use
a local file make sure that the path is correct.

File: node_modules@fullcalendar\google-calendar\index.js:2:0

ERROR #98124 WEBPACK

Generating development JavaScript bundle failed

Can’t resolve ‘@fullcalendar/core/index.js’ in
‘C:\TempSavio\Projects\Opensource\layer5\node_modules@fullcalendar\interaction’

If you’re trying to use a package make sure that ‘@fullcalendar/core/index.js’ is installed. If you’re trying to use a
local file make sure that the path is correct.

File: node_modules@fullcalendar\interaction\index.js:1:0

ERROR #98124 WEBPACK

Generating development JavaScript bundle failed

Can’t resolve ‘@fullcalendar/core/internal.js’ in
‘C:\TempSavio\Projects\Opensource\layer5\node_modules@fullcalendar\interaction’

If you’re trying to use a package make sure that ‘@fullcalendar/core/internal.js’ is installed. If you’re trying to use
a local file make sure that the path is correct.

File: node_modules@fullcalendar\interaction\index.js:2:0

failed Building development bundle - 12.340s
ERROR in ./node_modules/styled-components/dist/styled-components.browser.esm.js 1:0-73
Module not found: Error: Can’t resolve ‘react-is’ in
‘C:\TempSavio\Projects\Opensource\layer5\node_modules\styled-components\dist’
@ ./node_modules/gatsby-plugin-styled-components/gatsby-browser.js 7:24-52
@ ./.cache/api-runner-browser-plugins.js 4:10-86
@ ./.cache/api-runner-browser.js 3:14-53
@ ./.cache/app.js 13:0-65 31:87-35:1 39:20-29 91:0-14 114:17-26 149:6-15 31:0-35:2

ERROR in ./node_modules/@fullcalendar/google-calendar/index.js 1:0-77
Module not found: Error: Can’t resolve ‘@fullcalendar/core/index.js’ in
‘C:\TempSavio\Projects\Opensource\layer5\node_modules@fullcalendar\google-calendar’
@ ./src/sections/Community/Calendar/index.js 11:0-65 138:48-68
@ ./src/pages/community/calendar.js?export=head 17:11-54
@ ./.cache/this_is_virtual_fs_path/$virtual/async-requires.js 326:11-149
@ ./.cache/app.js 17:0-52 31:87-35:1 34:29-42 37:27-40 31:0-35:2

ERROR in ./node_modules/@fullcalendar/google-calendar/index.js 2:0-80
Module not found: Error: Can’t resolve ‘@fullcalendar/core/internal.js’ in
‘C:\TempSavio\Projects\Opensource\layer5\node_modules@fullcalendar\google-calendar’
@ ./src/sections/Community/Calendar/index.js 11:0-65 138:48-68
@ ./src/pages/community/calendar.js?export=head 17:11-54
@ ./.cache/this_is_virtual_fs_path/$virtual/async-requires.js 326:11-149
@ ./.cache/app.js 17:0-52 31:87-35:1 34:29-42 37:27-40 31:0-35:2

ERROR in ./node_modules/@fullcalendar/interaction/index.js 1:0-59
Module not found: Error: Can’t resolve ‘@fullcalendar/core/index.js’ in
‘C:\TempSavio\Projects\Opensource\layer5\node_modules@fullcalendar\interaction’
@ ./src/sections/Community/Calendar/index.js 10:0-58 138:29-46
@ ./src/pages/community/calendar.js?export=head 17:11-54
@ ./.cache/this_is_virtual_fs_path/$virtual/async-requires.js 326:11-149
@ ./.cache/app.js 17:0-52 31:87-35:1 34:29-42 37:27-40 31:0-35:2

ERROR in ./node_modules/@fullcalendar/interaction/index.js 2:0-964
Module not found: Error: Can’t resolve ‘@fullcalendar/core/internal.js’ in
‘C:\TempSavio\Projects\Opensource\layer5\node_modules@fullcalendar\interaction’
@ ./src/sections/Community/Calendar/index.js 10:0-58 138:29-46
@ ./src/pages/community/calendar.js?export=head 17:11-54
@ ./.cache/this_is_virtual_fs_path/$virtual/async-requires.js 326:11-149
@ ./.cache/app.js 17:0-52 31:87-35:1 34:29-42 37:27-40 31:0-35:2

develop compiled with 5 errors
success Writing page-data.json files to public directory - 2.508s - 2/791 315.39/s

Hey @Savio.Dias. Did you try make setup again before make site?

I have tried make setup before make site
Also I did deleted and cloned it again but the error exists.
I’ll shift to gitlab for some time …

What is your node version?

The error is saying module not found, either your node is outdated or your dependencies aren’t installed correctly.

@Savio.Dias

Yeah node was missing for WSL2 but present when I checked using cmd

For a better part i don’t think you need wsl for layer5 you could go simply windows, just try to update the node version and try to reclone repo and start again and add the path in environment variable if not set

Actually, contributing through GitLab works better for me now.

1 Like

can you please guide me how to start the layer5 project on gitlab? Im completely clueless did sign up its asking for ssh keys

It actually quite simple, just login in with github and then add the forked repoitory.

Although it is a very old issue and the author got the solution. For a newcomer if they get stuck in such situation. One fix might be to install nodejs, Gatsby in wsl2 (in case you are using wsl2) even though node is running perfectly on cmd. After that check the node version and Gatsby version for assurance and hit the make setup command. Enjoy contributing :tada:

Guys I m new to open source world…so my first step should be to set up the project locally? Right? And i m getting errors in that…what to do?

Can you specify what type of error you are facing?
If it is related to the build image being stuck at a certain percentage you can try out different ways to solve using wsl2 or using Layer5 repo in gitpod

can you elaborate what to do? step by step? sorry for asking but i am newbie

No worries.
I assume you have git clone the layer5 repo
Now login into gitpod and open the clone repo.
For using layer5 locally you can try out wsl2 solutions mentioned on discuss forum