<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tuan Duong</title>
    <description>The latest articles on DEV Community by Tuan Duong (@tuandm).</description>
    <link>https://dev.to/tuandm</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F136388%2F247bf4d5-e651-4994-b17d-0570f8b3e996.jpeg</url>
      <title>DEV Community: Tuan Duong</title>
      <link>https://dev.to/tuandm</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tuandm"/>
    <language>en</language>
    <item>
      <title>How to configure PHPStorm to work with Vite - Aliases</title>
      <dc:creator>Tuan Duong</dc:creator>
      <pubDate>Mon, 04 Nov 2024 04:04:00 +0000</pubDate>
      <link>https://dev.to/tuandm/how-to-configure-phpstorm-to-work-with-vite-aliases-4j86</link>
      <guid>https://dev.to/tuandm/how-to-configure-phpstorm-to-work-with-vite-aliases-4j86</guid>
      <description>&lt;p&gt;If you have trouble using "Declaration or Usages" hotkey to navigate to files importing from aliases while working with JS (or Vue) files, example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;&amp;lt;script setup&amp;gt;
import SomeComponent from '@/views/components/SomeComponent.vue'
...
&amp;lt;/script&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To resolve this, create a configuration file named phpstorm.config.js in your project's root directory with the following content:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;System.config({
  "paths": {
    "@/*": "./resources/js/*",
  }
});
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Ensure that the paths configuration aligns with the alias definitions in your &lt;code&gt;vite.config.js&lt;/code&gt;. For instance:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  resolve: {
      '@': fileURLToPath(new URL('./resources/js', import.meta.url)),
  ...
  }
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;By adding the &lt;code&gt;phpstorm.config.js&lt;/code&gt; file with the appropriate path mappings, PhpStorm will recognize the aliases, enabling seamless navigation using the "Declaration or Usages" hotkey.&lt;/p&gt;

</description>
      <category>phpstorm</category>
      <category>vite</category>
      <category>navigation</category>
    </item>
    <item>
      <title>Laravue core - a Laravel package to build a beautiful dashboard</title>
      <dc:creator>Tuan Duong</dc:creator>
      <pubDate>Thu, 21 Mar 2019 15:54:38 +0000</pubDate>
      <link>https://dev.to/tuandm/laravue-core---a-laravel-package-to-build-a-beautiful-dashboard-5aia</link>
      <guid>https://dev.to/tuandm/laravue-core---a-laravel-package-to-build-a-beautiful-dashboard-5aia</guid>
      <description>&lt;h1&gt;
  
  
  Laravue core
&lt;/h1&gt;

&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;Last month, I introduced our &lt;a href="https://github.com/tuandm/laravue" rel="noopener noreferrer"&gt;Laravue&lt;/a&gt; project which is to build an administrative interface for Laravel using VueJS in &lt;a href="https://dev.to/tuandm/laravel--vuejs--laravue---a-beautiful-dashboard-for-laravel-3h11"&gt;this post&lt;/a&gt;, the development progress is quite good and we have some beta releases last weeks. However, Laravue is positioned as an enterprise dashboard solution which is not suitable to use for existing projects. Today I would like to introduce &lt;a href="https://github.com/tuandm/laravue-core" rel="noopener noreferrer"&gt;Laravue core&lt;/a&gt; - a Laravel package which provides all core functionalities for Laravue and easy to integrate to any Laravel projects.&lt;/p&gt;

&lt;p&gt;Screenshot&lt;/p&gt;

&lt;p&gt;
  &lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fu3e01ftewf6x5jcn9aw8.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fu3e01ftewf6x5jcn9aw8.jpg"&gt;&lt;/a&gt;
&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Demo: &lt;a href="https://core.laravue.dev" rel="noopener noreferrer"&gt;https://core.laravue.dev&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Source code: &lt;a href="https://github.com/tuandm/laravue-core" rel="noopener noreferrer"&gt;https://github.com/tuandm/laravue-core&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Getting started
&lt;/h2&gt;

&lt;p&gt;Laravue-core provides a useful command that will set up everything, just get the &lt;code&gt;tuandm/laravue-core&lt;/code&gt; package with composer, type &lt;code&gt;php artisan laravue:setup&lt;/code&gt; then continue with the prompt - very easy.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7xejr1gqo6mjotkw9152.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7xejr1gqo6mjotkw9152.gif" alt="Laravue setup"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Please refer to the &lt;a href="https://github.com/tuandm/laravue-core#installing" rel="noopener noreferrer"&gt;installation guide&lt;/a&gt; for more detail&lt;/p&gt;

&lt;h2&gt;
  
  
  Next steps
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;We will try to release new version for &lt;a href="https://lumen.laravel.com/" rel="noopener noreferrer"&gt;Lumen&lt;/a&gt; - it is very attractive.&lt;/li&gt;
&lt;li&gt;Tests system is under development - we want to cover this library as much as possible&lt;/li&gt;
&lt;li&gt;Documentation will be released shortly - including components manual and development guidelines. &lt;/li&gt;
&lt;li&gt;We will add useful Laravel packages such as spatie/laravel-permission or CRUD support.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;I hope this package will help you in building a beautiful admin UI for your Laravel projects. I greatly appreciate any feedback, comments, suggestions and even stars,... they absolutely make me and this library better. Thank you.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>laravel</category>
      <category>php</category>
      <category>vue</category>
      <category>showdev</category>
    </item>
    <item>
      <title>How to test Vue components with Laravel Mix and Mocha</title>
      <dc:creator>Tuan Duong</dc:creator>
      <pubDate>Wed, 06 Mar 2019 15:33:56 +0000</pubDate>
      <link>https://dev.to/tuandm/how-to-test-vue-components-with-laravel-mix-and-mocha-3kgc</link>
      <guid>https://dev.to/tuandm/how-to-test-vue-components-with-laravel-mix-and-mocha-3kgc</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;While adding tests to &lt;a href="https://github.com/tuandm/laravue"&gt;Laravue&lt;/a&gt;, I found that setting unit tests for Vue with Laravel Mix is not simple like &lt;a href="https://vuejs.org/v2/guide/unit-testing.html"&gt;Vue's official document&lt;/a&gt;. After working around with some google-ing, I've passed the setup steps and just want to share what I've done so far.&lt;/p&gt;

&lt;h2&gt;
  
  
  Setup Laravel and npm dependencies
&lt;/h2&gt;

&lt;p&gt;Firstly, we create new Laravel project with &lt;a href="https://laravel.com/docs/5.8/installation#installing-laravel"&gt;the command&lt;/a&gt; which every Laravel developer shoud know:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;composer create-project --prefer-dist laravel/laravel test
cd test
npm install
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Very easy!&lt;/p&gt;

&lt;p&gt;Then we have to setup tests environment as well as required libraries/dependencies. I picked &lt;a href="https://vue-test-utils.vuejs.org/guides/#testing-single-file-components-with-mocha-webpack"&gt;Mocha + Webpack&lt;/a&gt; because many articles mentioned this.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npm install --save-dev webpack vue-template-compiler @vue/test-utils mocha mocha-webpack jsdom jsdom-global expect
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Ok, seems everything is set, let us double check with &lt;code&gt;npm list --depth=0&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Wow, something is wrong!&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;➜  test npm list --depth=0
...
├── UNMET PEER DEPENDENCY mocha@6.0.2
...
└── UNMET PEER DEPENDENCY webpack@4.29.6

npm ERR! peer dep missing: mocha@&amp;gt;=2.4.5 &amp;lt;=5, required by mocha-webpack@1.1.0
npm ERR! peer dep missing: webpack@^2.0.0 || ^3.0.0, required by mocha-webpack@1.1.0
npm ERR! peer dep missing: webpack@^2.0.0 || ^3.0.0, required by mocha-webpack@1.1.0
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;It says that dependencies' versions are not matched. Seems mocha-webpack is not up-to-date with webpack and mocha, it requires old versions (mocha 2.4.5-5 and webpack 2 or 3 while latest versions are mocha@6 and &lt;a href="mailto:webpack@2.49.6"&gt;webpack@2.49.6&lt;/a&gt;). Now let's go to the &lt;a href="https://github.com/zinserjan/mocha-webpack"&gt;mocha-webpack&lt;/a&gt; repo to see what happens. Indeed, there is no update since last year. Ok, what to do next? We may want to check the issue list to see any similar cases and solutions. Luckily, the &lt;a href="https://github.com/zinserjan/mocha-webpack/issues/308"&gt;first issue&lt;/a&gt; is the one we are finding:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Hi there, mocha-webpack users!

mocha-webpack has no activity since May, 2018. We at SysGears are maintaining a fork here:
https://github.com/sysgears/mochapack

A new version of mochapack@1.1.0 has been released today with Mocha 6 support.

Check it out!
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Now we go to &lt;a href="https://github.com/sysgears/mochapack"&gt;Mochapack&lt;/a&gt;  as the author recommended, we can see the installation guide for Mochapack:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npm install --save-dev mochapack
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Seems it works. Ok, let's remove the outdated mocha-webpack:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npm remove mocha-webpack
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Wow, &lt;code&gt;npm list --depth=0&lt;/code&gt; returns very clean result. Don't forget to give the mochapack a star for this awesome work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Setup test enviroment
&lt;/h2&gt;

&lt;p&gt;Now we are ready to create test cases for our Vue components following this &lt;a href="https://vue-test-utils.vuejs.org/guides/#testing-single-file-components-with-mocha-webpack"&gt;guide&lt;/a&gt;. To start it, we have to prepare a environment for tests by creating new folder inside &lt;code&gt;/tests/&lt;/code&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mkdir tests/js
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Then create file &lt;code&gt;setup.js&lt;/code&gt; inside folder &lt;code&gt;tests/js&lt;/code&gt; and put this line on top:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;require('jsdom-global')();
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Next step will be the npm command to run tests, we have to open &lt;code&gt;package.json&lt;/code&gt; and add this line inside &lt;code&gt;scripts&lt;/code&gt; section&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;        "test": "mochapack --webpack-config=node_modules/laravel-mix/setup/webpack.config.js --require tests/js/setup.js tests/js/\\*\\*/\\*.spec.js"
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;You can pick any name for &lt;code&gt;tests/js&lt;/code&gt; folder and &lt;code&gt;setup.js&lt;/code&gt; file, don't forget to indicate them in the test command&lt;/p&gt;

&lt;p&gt;Now is the show time:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;➜ npm test

 WEBPACK  Compiled successfully in 140ms

 MOCHA  Testing...



  0 passing (0ms)

 MOCHA  Tests completed successfully

&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Wow, it works with 0 test passing - because we haven't added yet. We are going to do it now.&lt;/p&gt;

&lt;h2&gt;
  
  
  Writing a test
&lt;/h2&gt;

&lt;p&gt;To save time, we can use &lt;code&gt;resources/js/components/ExampleComponent.vue&lt;/code&gt; of Laravel to write test. If you take a look to this component, you will see it just shows the &lt;code&gt;Example Component&lt;/code&gt; header. Now we create a test file &lt;code&gt;tests/js/components/ExampleComponent.spec.js&lt;/code&gt; and put these lines to that file&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;// tests/js/components/ExampleComponent.spec.js
import { mount } from '@vue/test-utils';
import expect from 'expect';
import ExampleComponent from '../../../resources/js/components/ExampleComponent.vue';

describe('ExampleComponent.vue', () =&amp;gt; {
  it('says that it is an example component', () =&amp;gt; {
    const wrapper = mount(ExampleComponent);
    expect(wrapper.html()).toContain('Example Component');
  });
});
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;This test case is to check after ExampleComponent mounted, &lt;code&gt;Example Component&lt;/code&gt; should be in the output html.&lt;/p&gt;

&lt;p&gt;Save the file and run the test command again:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;➜ npm test
 WEBPACK  Failed to compile with 1 error(s)

Error in ./resources/js/components/ExampleComponent.vue?vue&amp;amp;type=template&amp;amp;id=299e239e&amp;amp;

  Module build failed (from ./node_modules/vue-loader/lib/loaders/templateLoader.js):
  TypeError: Super expression must either be null or a function
      at /.../test/node_modules/prettier/index.js:40358:5
      at /.../test/node_modules/prettier/index.js:40378:4

npm ERR! Test failed.  See above for more details.
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Ok, we've got the error. You will be crazy to find out the answer for this error from internet. Don't worry, just do this fix: Open &lt;code&gt;tests/js/setup.js&lt;/code&gt; again and put this line next to the first one:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;window.Date = Date;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Save &lt;code&gt;setup.js&lt;/code&gt; file and run test command again&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;➜ npm test

 WEBPACK  Compiled successfully in 1436ms

 MOCHA  Testing...



  ExampleComponent.vue
Component mounted.
    ✓ says that it is an example component


  1 passing (22ms)

 MOCHA  Tests completed successfully
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Yeah, it works, test case passed. Now we can put more Vue components and tests them.&lt;/p&gt;

&lt;p&gt;Please enjoy testing! You can find my sample here: &lt;a href="https://github.com/tuandm/laravel-vue-tests-with-mocha"&gt;https://github.com/tuandm/laravel-vue-tests-with-mocha&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Noted: I'm using MacOS Mojave 10.14.2, all related tools (npm, composer...) are considered as last versions.&lt;/p&gt;

</description>
      <category>laravel</category>
      <category>php</category>
      <category>vue</category>
      <category>test</category>
    </item>
    <item>
      <title>Laravue - a beautiful dashboard for Laravel</title>
      <dc:creator>Tuan Duong</dc:creator>
      <pubDate>Thu, 14 Feb 2019 05:43:39 +0000</pubDate>
      <link>https://dev.to/tuandm/laravel--vuejs--laravue---a-beautiful-dashboard-for-laravel-3h11</link>
      <guid>https://dev.to/tuandm/laravel--vuejs--laravue---a-beautiful-dashboard-for-laravel-3h11</guid>
      <description>&lt;h3&gt;
  
  
  Introductions
&lt;/h3&gt;

&lt;p&gt;Couple months ago I was trying to find a new solution for my project, and I had built a SPA dashboard with Vue (using this &lt;a href="https://github.com/PanJiaChen/vue-element-admin" rel="noopener noreferrer"&gt;great framework&lt;/a&gt;, Laravel &lt;a href="https://lumen.laravel.com/" rel="noopener noreferrer"&gt;Lumen&lt;/a&gt; as API gateway, Laravel &lt;a href="https://laravel.com/docs/5.7/passport" rel="noopener noreferrer"&gt;Passport&lt;/a&gt; as SSO server). After some weeks of working, I found that architecture has some limitations, especially in deployment and hard to open source (because many components involved, CORS setup,...). Then one day new idea came to me: &lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Why don't we use builtin VueJS of Laravel to build a SPA dashboard?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And Laravel + VueJS = &lt;a href="https://github.com/tuandm/laravue" rel="noopener noreferrer"&gt;Laravue&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Demo: &lt;a href="https://laravue.dev" rel="noopener noreferrer"&gt;https://laravue.dev&lt;/a&gt;&lt;br&gt;
Documentation: &lt;a href="https://doc.laravue.dev" rel="noopener noreferrer"&gt;https://doc.laravue.dev&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fk8xbnmrpaokp8n1vbk85.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fk8xbnmrpaokp8n1vbk85.png" title="Laravue" alt="Laravue"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/tuandm/laravue" rel="noopener noreferrer"&gt;Laravue&lt;/a&gt; is a beautiful dashboard inspired by &lt;a href="https://github.com/PanJiaChen/vue-element-admin" rel="noopener noreferrer"&gt;vue-element-admin&lt;/a&gt; but beyond that. It provides all necessary components for building an enterprise application for admin to control business and manage others. My plan is to apply newest technologies/libraries/components of Laravel/Vue to this project and make it easy to use for everyone. In the demo, API will be served by Laravel itself and most of them are faked - but easy to implement.&lt;/p&gt;

&lt;h3&gt;
  
  
  Getting started
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# Clone the project with composer
composer create-project tuandm/laravue
cd laravue

# Migration and DB seeder (after changing your DB settings in .env)
php artisan migrate --seed

# Install passport
php artisan passport:install

# install dependency
npm install

# Build for development
npm run dev # or npm run watch

# Start local development server
npm artisan serve
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Next steps
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;This project is on heavy development and it has not being built as Laravel plugin (as it should be). Next step will be a standalone plugin for Laravel to easy to integrate to existing Laravel websites.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Provide full documentation and strict coding convention. PHP/Laravel has an excellent &lt;a href="https://www.php-fig.org/psr/" rel="noopener noreferrer"&gt;PSR&lt;/a&gt; and VueJS has a good standard &lt;a href="https://vuejs.org/v2/style-guide/" rel="noopener noreferrer"&gt;here&lt;/a&gt; but it's too basic and not enough.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Fully tests.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  I greatly appreciate any feedback, comments, suggestions,... they absolutely make me and this library better. Thank you.
&lt;/h4&gt;

&lt;p&gt;Also, this is my first DEV post 🎉&lt;/p&gt;

</description>
      <category>vue</category>
      <category>laravel</category>
      <category>php</category>
      <category>dashboard</category>
    </item>
  </channel>
</rss>
