codesandbox / codesandbox/codesandbox-client

Add fnm support and update yarn.

Open
#8,142 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🌈 Feature

Add fnm support and update yarn-3 to Codesandbox-client this feature should IMHO

  • allow test against multiple versions of node
  • shrinking code size
  • make maintenance easier

I believe the latest version of yarn is supposed to increase build speed and reduce the amount of date needed with the use of plug and play. I think that would be great if we supported this but in order to do that I need to use a new version of node while trying to keep compatibility.

IMHO it is a good to test node

  • on old programs as you can. --> Allow for easy use.
  • test against the latest releases. --> Allows for lesser bugs.
  • against the latest releases. -->Allow for less code deletion and rewrites and use newer tools a.k.a yarn 3 plug N play.

I want to run a script to just that.

You have examples or an idea how it can be implemented? -->

I am to do that on my fork right now here. But I came acrossed some issues here and here

On my work on this, I moved the Dockerfile out of the .Docker directory easily and put it in The developer dir . I am play with a lot of the new features on developer container .

While it is easy to install FNM in a docker image it is not easy to run eval. My first attempt was put the eval in /root/.zshtc docker file which didn't really work it was got rid of. I tried putting it in a lot of different places and I could not get this to work

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Dockerfile location in the .Docker directory and the developer container changes described in the issue, then compare the fork linked in the report and the related issues #8128 and #8074. Done should include a reproducible way to test multiple Node versions and an updated Yarn setup, with compatibility and build-size effects verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, javascript, node.js
Domain
build-system, devops, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.