[Feat]: Why does Yarn install always fail after Git clone #6194

Activity

1. zxytt

   added

   enhancementSome improvement that isn't a featureSome improvement that isn't a feature

   on May 8, 2023
2. zxytt

   changed the title [-][Feat]: Why cannot I debug projects locally after Git clone？[/-] [+][Feat]: Why does Yarn install always fail after Git clone[/+] on May 8, 2023
3. code-asher commented on May 8, 2023

   

   code-asher

   on May 8, 2023

   Member

   More actions

   Can you provide reproduction steps? What error do you get? It seems unlikely this would be caused by code-server.
4. code-asher

   added

   waiting-for-infoWaiting for more information from submitterWaiting for more information from submitter

   and removed

   enhancementSome improvement that isn't a featureSome improvement that isn't a feature

   on May 8, 2023
5. zxytt commented on May 9, 2023

   

   zxytt

   on May 9, 2023

   Last edited by zxytt

   Author

   More actions

   After the Yarn build is completed, the Yarn watch will start and access the link as shown in
   
   This package always cannot be built, and occasionally it can.
   
   After building it, accessing the URL will result in the following error
   
6. code-asher commented on May 9, 2023

   

   code-asher

   on May 9, 2023

   Member

   More actions

   Ohhh I see! The 404 is because VS Code takes much longer to compile than the web server. You will need to wait for a "Finished compilation" message (there will be two, one for the built-in extensions and another for VS Code itself). We should detect this and show a better error message though.

   The "forbidden" error is because you have not applied the patches to VS Code. https://github.com/coder/code-server/blob/main/docs/CONTRIBUTING.md#troubleshooting
7. coder

   locked and limited conversation to collaborators on May 9, 2023
8. code-asher

   converted this issue into a discussion #6200 on May 9, 2023