Yii2 VS Nuxt 3

Yii is one of the oldest PHP frameworks, acronym as Yes It Is! It has 14.2k stars and 7k forks on GitHub. It is a fast, secure, and flexible PHP framework for web development, especially for building MVC architecture websites. It is an Object-Oriented PHP framework that requires knowledge of inheritance, polymorphism, etc.

In Yii Framework we have a middleware that will allow us to access our applications without the need to point the web server to the public directory of each template, so we will use the middleware SubFolder::class.

asset-packagist: This is the traditional Yii2 way, here we will add the following to our composer.json.

It is often preferable to manage Yii Assets programmatically. For example, when you use the widget in a page, it will automatically include the required css and javascript files, instead of asking you to manually find these files and include them. And when you upgrade the widget to a new version, it will automatically use the new version of the Yii Assets. In this tutorial, we will describe the powerful Yii Assets management capability provided in Yii Framework .

As we can see in the example above, we have defined the configuration of our packages in files .php (it doesn’t matter if they are YiiFramework packages or not), this allows us to define the configuration of each component in a very simple way to understand.

Now if we want to create an extension, under the code standard used in the Yii Framework v.3 packages, we can use yiisoft/template, provides us the tools necessary for our code to comply with good coding standards they are:

Now we understand how to do any configuration of any YiiFramework package or external, it is not necessary to have a single long and complex configuration file, we can organize it according to the group of configurations and Yii config will do the work for you, as well as the container it applies the definitions for you, with the automatic wiring facility in controllers, which makes it easy to access any container dependency without the need to use static access to it, or depend on the container itself.

- https://github.com/nuxt/framework: An intuitive framework for building web applications, built for the edge.

It uses Nuxi for Command line interface,

Note, the repo linked below, https://github.com/danielroe/nuxt-zero-js, was an experiment that I subsequently moved into Nuxt core: https://github.com/nuxt/framework/pull/7248. I plan to update it to test out per-route zero-JS via a route rule.

I asked this before on the Github discussion https://github.com/nuxt/framework/discussions/10073, but I haven't found an answer yet.

Also one I've reported a long time ago, that's still an issue today: If you start the Nuxt dev server without create the server/ folder, Nuxt isn't going to be able to read any of your server/api files. You have to create the folder and restart the dev server. Only then, it will start detecting your server files. This is an issue on both Windows and Linux.

Perhaps this thread can help you.

But there is a catch, nuxt.config does not allow functions in it. And it could be bother to mention this in every single page. Also, the later part is supposed to act like a Default or Fallback. Hmm.. Now what? Well, that where plugins system comes in. I can create a Plugin named title and add this logic there, which will be implemented on every page. Also, Nuxt devs mentioned this approach here.

I've found a matching issue with a solution I can use as a hotfix for now: https://github.com/nuxt/framework/issues/6648

https://github.com/nuxt/framework/issues/3587 (upstream Vue bug maybe?) https://github.com/nuxt/framework/issues/8634 https://github.com/nuxt/framework/issues/8611

This issue is where I started, and I noticed that in my project, setting the cookie header manually, or through a composable on the server-side doesn't actually set it in the browser (it doesn't show up in the developer tools). They've listed workarounds, but they're just that - the first link (when it comes back up, will show a messy composable you can write). Everything works fine with `axios` (instead of their built-in data fetching APIs), but the request seems to be executed twice on page load for some reason.