Clones a remote repository to use as the TypeScript application source.
Runs npm test to determine whether the challenge is solved.
What's inside:
The whole thing is built on top of the codercom/code-server container - that's the one that runs the VSCode server.
During the setup phase, it installs Node.js to the container, clones the repository containing the application we'll be running our tests against, and installs its dependencies. It also corrupts one of the application files to make the tests fail (it felt more appropriate to keep the application example in the remote repository fully functional).
During the check phase, it runs npm tests and exits with a success code if the tests pass.
During the solve phase, it checks out the working version of the corrupted file from the git tree.
Introduces a basic VSCode / TypeScript template.
Features:
npm testto determine whether the challenge is solved.What's inside:
The whole thing is built on top of the
codercom/code-servercontainer - that's the one that runs the VSCode server.During the setup phase, it installs Node.js to the container, clones the repository containing the application we'll be running our tests against, and installs its dependencies. It also corrupts one of the application files to make the tests fail (it felt more appropriate to keep the application example in the remote repository fully functional).
During the check phase, it runs
npm testsand exits with a success code if the tests pass.During the solve phase, it checks out the working version of the corrupted file from the git tree.
There is not cleanup to be done.
Possible TODOs: