<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Project on Stefan Ukena's Blog</title><link>https://blog.ukena.de/tags/project/</link><description>Recent content in Project on Stefan Ukena's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 31 Oct 2021 08:00:00 +0100</lastBuildDate><atom:link href="https://blog.ukena.de/tags/project/index.xml" rel="self" type="application/rss+xml"/><item><title>Teaching myself frontend development: What I learned this week</title><link>https://blog.ukena.de/posts/2021/10/teaching-myself-frontend-development-04/</link><pubDate>Sun, 31 Oct 2021 08:00:00 +0100</pubDate><guid>https://blog.ukena.de/posts/2021/10/teaching-myself-frontend-development-04/</guid><description>&lt;p&gt;This week I struggled with getting vue to work with the most recent release of tailwind css. I was surprised to stumble into these kinds of problems this early in my first project. Usually, setting up a fresh project is pretty straight forward. But I completely undertestimated the complexity of frontend tooling. I went in with the idea that using straight &lt;code&gt;npm&lt;/code&gt; would be a safe bet. However, the tailwind documentation refers to &lt;code&gt;vite&lt;/code&gt; and &lt;code&gt;npm&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>