jmarlow4 / 4kings-svelte

Implementation of 4 kings challenge with Svelte v3!

Four Kings Code Challenge

Draw All The Kings!

Use the endpoint:

https://deckofcardsapi.com/api/deck/new/draw/?count=0

to shuffle a new deck of cards. This will return a deck_id property which you will then use to draw 2 cards from the deck. Use the endpoint

https://deckofcardsapi.com/api/deck/{{deck_id}}/draw/?count=2

to draw two cards from the deck. You must insert the deck_id from the response from calling the first into the {{deck_id}} url in order to draw cards from that deck. Draw cards every second until you get all of the Kings and then stop drawing cards.

Keep track of the cards drawn and have some way of alerting the user when all of the kings are drawn.

Sort the drawn cards into suits and sort them like so : [ACE, 2, 3, 4, 5, 6, 7, 8, 9, 10, JACK, QUEEN, KING] for each suit.

Looking for a shareable component template? Go here --> sveltejs/component-template

---

svelte app

This is a project template for Svelte apps. It lives at https://github.com/sveltejs/template.

To create a new project based on this template using degit:

npx degit sveltejs/template svelte-app
cd svelte-app

Note that you will need to have Node.js installed.

Get started

Install the dependencies...

cd svelte-app
npm install

...then start Rollup:

npm run dev

Navigate to localhost:5000. You should see your app running. Edit a component file in src, save it, and reload the page to see your changes.

By default, the server will only respond to requests from localhost. To allow connections from other computers, edit the sirv commands in package.json to include the option --host 0.0.0.0.

Building and running in production mode

To create an optimised version of the app:

npm run build

You can run the newly built app with npm run start. This uses sirv, which is included in your package.json's dependencies so that the app will work when you deploy to platforms like Heroku.

Single-page app mode

By default, sirv will only respond to requests that match files in public. This is to maximise compatibility with static fileservers, allowing you to deploy your app anywhere.

If you're building a single-page app (SPA) with multiple routes, sirv needs to be able to respond to requests for any path. You can make it so by editing the "start" command in package.json:

"start": "sirv public --single"

Deploying to the web

With now

Install now if you haven't already:

npm install -g now

Then, from within your project folder:

cd public
now deploy --name my-project

As an alternative, use the Now desktop client and simply drag the unzipped project folder to the taskbar icon.

With surge

Install surge if you haven't already:

npm install -g surge

Then, from within your project folder:

npm run build
surge public my-project.surge.sh