Learn the foundational tools and skills of building web applications
In this workshop we'll go through exercises in a real world app that will
help you learn some key concepts for building web applications.
<a alt="Epic Web logo with the words Deployed Version" href="https://foundations.epicweb.dev/"
<img width="300px" src="https://github-production-user-asset-6210df.s3.amazonaws.com/1500684/254000390-447a3559-e7b9-4918-947a-1b326d239771.png" />
All of these must be available in your PATH. To verify things are set up
properly, you can run this:
git --version
node --version
npm --version
If you have trouble with any of these, learn more about the PATH environment variable and how to fix it here for windows or mac/linux.
Use the Epic Workshop CLI to get this setup:
```sh nonumber npx --yes epicshop@latest add full-stack-foundations
If you experience errors here, please open [an issue][issue] with as many
details as you can offer.
## Exercises
You'll find all the exercises in the `exercises` directory. The structure of the
workshop apps is described below, but most of the time you should be able to
simply run the app and navigate around the different exercises using the
application (there are even buttons to open the right exercise file right in
your editor).
The purpose of the exercise is **not** for you to work through all the material.
It's intended to get your brain thinking about the right questions to ask me as
_I_ walk through the material.
## Running the app
To get the app up and running (and really see if it worked), run:
```shell
npm start
Now open your browser to the address that's logged out for you and you're good to get started!
The test script in the package.json runs the tests on the solutions (these
should all pass). To run the tests against your own work, you simply open the
problem page and click the "Test" tab.
The application has several buttons which will launch your editor to the right file. There are a lot of files in this workshop so you'll be using this feature a lot to get to the right place at the right time.
This should just work™️ (it looks at your currently running processes and
chooses the editor based on that). If it doesn't guess correctly, create a
.env file in the root of this project and add an environment variable called
EPICSHOP_EDITOR with the value being set to the path to your editor's
executable. For example, if you're using VS Code on Windows, you'd add this to
your .env file:
EPICSHOP_EDITOR='"C:\Program Files\Microsoft VS Code\bin\code.cmd"'
Make certain that if the path includes spaces that you wrap the path in quotes as above (note the use of single quotes wrapping the double quotes!).
The value of EPICSHOP_EDITOR should be the command that you would run in your
terminal to open your editor from the command line. This means, the first thing
should be the path to the executable for your editor (or the command if you have
one in your PATH). So you may be able to get away with doing something as
simple as this:
EPICSHOP_EDITOR=code
exercises/*.*/README.md: Exercise background informationexercises/*.*/*.problem.*/README.*.md: Problem Instructionsexercises/*.*/*.problem.*/*.tsx: Exercise with Emoji helpers 👈 You spend
most of your time here.exercises/*.*/*.solution.*/*.tsx: Solved versionThe purpose of the exercise is not for you to work through all the material. It's intended to get your brain thinking about the right questions to ask me as I walk through the material.
Each exercise has comments in it to help you get through the exercise. These fun emoji characters are here to help you.
Each exercise has an Elaboration and Feedback link. Please fill that out after the exercise and instruction.
At the end of the workshop, please go to this URL to give overall feedback. Thank you! https://kcd.im/rmx-workshop-ws-feedback
$ claude mcp add full-stack-foundations \
-- python -m otcore.mcp_server <graph>