<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[NitroEvil]]></title><description><![CDATA[Self taught full stack developer since 2020, this was a passion to get into development after working as 1st, 2nd line Support.]]></description><link>https://blog.clarkee.dev</link><generator>RSS for Node</generator><lastBuildDate>Tue, 07 Apr 2026 10:07:57 GMT</lastBuildDate><atom:link href="https://blog.clarkee.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Rebuild of clarkee.dev]]></title><description><![CDATA[So after a long time coming I’ve finally gotten around to building a better website for myself. Now the site is in it’s most basic form but what else do you need?
The previous site was built on a old version of React and it only had the standard Reac...]]></description><link>https://blog.clarkee.dev/rebuild-of-clarkeedev</link><guid isPermaLink="true">https://blog.clarkee.dev/rebuild-of-clarkeedev</guid><category><![CDATA[website]]></category><category><![CDATA[Nuxt]]></category><category><![CDATA[Nuxt.js]]></category><category><![CDATA[personal]]></category><category><![CDATA[GitHub]]></category><category><![CDATA[github copilot]]></category><category><![CDATA[GitHubPages]]></category><category><![CDATA[github-actions]]></category><dc:creator><![CDATA[Thomas Clarke]]></dc:creator><pubDate>Sun, 14 Dec 2025 11:23:44 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/stock/unsplash/npxXWgQ33ZQ/upload/f6c0ea7df7757d0c703cc91fd94a14c7.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>So after a long time coming I’ve finally gotten around to building a better website for myself. Now the site is in it’s most basic form but what else do you need?</p>
<p>The previous site was built on a old version of React and it only had the standard React app loading screen. So this didn’t really produce anything meaningful.</p>
<h2 id="heading-the-why">The why</h2>
<p>React had multiple CVEs as of Q4 of 2025, this was causing GitHub security scanning to complain non stop about the site even though it didn’t have anything meaningful or the attention of viewers.</p>
<p>I wanted to rebuild the website for a long time but due to other interests I never got around to it, so it stayed as it’s current dormant self.</p>
<p>Rebuilding the website would also bring it in line for the other apps I build for work, which are all based on NUXT/Vue.js.</p>
<h2 id="heading-why-nuxtvuejs">Why Nuxt/Vue.js</h2>
<p>I’ve liked react for a long time, but there are many dependencies required for building the a site, even thought the site is basic in nature. I always wanted to be able to expand this into other forms. Nuxt could with a lot of batteries included and I find it a much more enjoyable experience to use, which also aligns with my dotnet background. Now I could use NEXT.js but it’s still react under the hood, I’m not a fan of the layout behind React where functions return html, which also has nested functions within to build the html element.</p>
<h2 id="heading-v0">V0</h2>
<p>Now I used V0 to design the site, but I gave it some basic info on myself, which the current design aligned with what I wanted. Though with all A.I you always need to adjust the output, some of the issues I had was</p>
<ul>
<li><p>Anchor links was scrolling to the block instantly with no transition.</p>
</li>
<li><p>It used <code>’</code> rather than <code>”</code> which I’m for double quotes over single quotes.</p>
</li>
<li><p>The styling was based on Tailwind CSS, now site looked identical but NUXT UI was the correct way forward.</p>
</li>
<li><p>Scrolling was sharp and not smooth (I thought I needed a lib to handle this)</p>
</li>
</ul>
<p>I asked V0 to adjust the markup to be based on the NUXT UI lib which it imported the NUXT UI lib into app.vue which isn’t required as the NUXT will also import. Though this can make it easier to understand where components are coming from.</p>
<h2 id="heading-github-pr-with-co-pilot">GitHub PR with Co-Pilot</h2>
<p>Once all the work was complete and the PR was created, Co-Pilot scanned the changes and identified that it used anchor links for scrolling and suggests to create a PR to fix this, it also found that the styling was done in the `app.vue` rather than in the `main.css` file.</p>
<p>So co-pilot created a new PR in draft awaiting me to review what it was going to do, on approving the go ahead the changes was made and the PR was live. I pulled this PR down tested the scrolling and 💥I had nice scrolling. This PR was then merged into the PR for nuxt migration.</p>
<h2 id="heading-deployment">Deployment</h2>
<p>The site <a target="_blank" href="https://clarkee.dev">https://clarkee.dev</a> is hosted via GitHub pages, so a deployment action was created for this deployment using NUXT.js deployment example, which builds the site as static assets and deploys the app.</p>
]]></content:encoded></item><item><title><![CDATA[Auth0 not skipping consent for local development]]></title><description><![CDATA[So I've been working on a personal project working with React and FastAPI. Now I've hit an issue we're 1st party application would require consent regardless if the Allow Skipping User Consent was set to true or not. I was then questioning myself if ...]]></description><link>https://blog.clarkee.dev/auth0-not-skipping-consent-for-local-development</link><guid isPermaLink="true">https://blog.clarkee.dev/auth0-not-skipping-consent-for-local-development</guid><category><![CDATA[Auth0]]></category><dc:creator><![CDATA[Thomas Clarke]]></dc:creator><pubDate>Sat, 27 Mar 2021 19:22:20 GMT</pubDate><content:encoded><![CDATA[<p>So I've been working on a personal project working with React and FastAPI. Now I've hit an issue we're 1st party application would require consent regardless if the <code>Allow Skipping User Consent</code> was set to true or not. I was then questioning myself if this was the correct approach for Role Based Access Control (RBAC) between the frontend and backend. I could use the permissions option within Auth0 but didn't feel right. I could also not find anyone else talking about this approach. </p>
<p>After a fair few days of Googling and reading articles looking at the best way to go about Authorization between the frontend and backend, I come across <a target="_blank" href="https://dev.to/kleeut/skipping-auth0-consent-prompt-for-local-development-524k">this</a> DEV article what explains how to skip Auth0 consent prompt for local development.</p>
<p>I wasn't aware that Auth0 blocks localhost, I never come across any docs that stated this.</p>
<p>Setting up NGROK to then test resulted in the expected behaviour for 1st party applications.  </p>
]]></content:encoded></item></channel></rss>