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
tomoyafujita@~/DVT/03_OSS/github.com/fujitatomoya/website >yarn
00h00m00s 0/0: : ERROR: There are no scenarios; must have at least one.
tomoyafujita@~/DVT/03_OSS/github.com/fujitatomoya/website >yarn build
00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'build'
To Reproduce
tomoyafujita@~/DVT/03_OSS/github.com/fujitatomoya/website >yarn
00h00m00s 0/0: : ERROR: There are no scenarios; must have at least one.
tomoyafujita@~/DVT/03_OSS/github.com/fujitatomoya/website >yarn build
00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'build'
Expected behavior
documentation should be built and previewed by localserver before pushing the development branch.
Screenshots
Desktop (please complete the following information):
OS: Ubuntu 20.04
Browser: N.A
Version: N.A
Additional context
I think it would be more useful and developer-friendly that we could provide build-container or devcontainer, so that users do not need to set up the environment for this doc development.
The text was updated successfully, but these errors were encountered:
I can't reproduce this in my local environment. I searched for this error, it seems to be caused by the yarn version being lower than 1.22, what's your yarn version?
Describe the bug
I was following https://github.com/kubeedge/website?tab=readme-ov-file#previewing-your-changes-on-a-local-website-server but it failed with the error.
To Reproduce
Expected behavior
documentation should be built and previewed by localserver before pushing the development branch.
Screenshots
Desktop (please complete the following information):
Additional context
I think it would be more useful and developer-friendly that we could provide build-container or devcontainer, so that users do not need to set up the environment for this doc development.
The text was updated successfully, but these errors were encountered: