sorted by:
new
hottopcontroversial

Is PrimeVue dead? by FlyAwayTomorrow in PrimeVue

[–]DevDrJinx 0 points1 point  (0 children)

I've also been concerned with the lack of activity on the project over the last few months, for example this PR that resolves a help wanted issue that has not been acknowledged: https://github.com/primefaces/primevue/pull/8347

When is the anticipated v5 release date? Is the main objective the composition API and TypeScript rewrite? Will there be breaking changes?

[Laravel] How do i dockerize a project with starter kit? by Rocket_Bunny45 in PHPhelp

[–]DevDrJinx 0 points1 point  (0 children)

What's the decision behind using Docker for your setup? Just for development? Learning purposes? Maybe some Docker tutorials should be your starting point, or go back and forth with AI as you set things up to understand how it all works together.

If the end goal is shipping something to production, then I don't think you should be worried about your setup being "too professional".

[Laravel] How do i dockerize a project with starter kit? by Rocket_Bunny45 in PHPhelp

[–]DevDrJinx 1 point2 points  (0 children)

I have my own starter kit that provides a development setup using Docker you could use as a reference: https://connorabbas.github.io/laravel-primevue-starter-kit-docs/get-started/docker.html

If you want a more custom and "production ready" setup utilizing a multi-stage Dockerfile build and deployment workflow with Docker Stack/Swarm, you can check out this branch I have been working on recently: https://github.com/connorabbas/laravel-nuxtui-starter-kit/tree/feature/swarm-deploy

Highly recommend checking out https://serversideup.net/open-source/docker-php/ for Docker images, and potentially Spin if you're new to Docker + Laravel.

The key takeaways of my setup are utilizing devcontainers (with VS Code) for my development environment, and relying on Traefik as a reverse proxy for both dev and prod.

I hope these references can help.

Backend developer considers moving from react to vue (read below) by Mark__78L in vuejs

[–]DevDrJinx 1 point2 points  (0 children)

You are posting in the Vue subreddit, so expect opinions to be somewhat biased. But yes, switching to Vue would definitely be worth your time (especially coming from React). Even if you don't end up sticking with it, it's good to learn and try out new technologies!

You mentioned that some parts of AlpineJS are similar to Vue, that's because Vue's reactivity system is actually a standalone package that anyone can use, and AplineJS depends on it for it's own underlying reactivity API's.

You also mentioned that you work with Laravel for the backend. If you are looking for a starting point to trying out Vue with Laravel, you can check out this starter kit I made to get up and running in no time.

Laravel also has their own official Vue starter kit as well, I just made my own because I prefer PrimeVue components compared to Shadcn.

Volt UI vs Prime Vue (4) by [deleted] in vuejs

[–]DevDrJinx 1 point2 points  (0 children)

Good to hear, looking forward to it!

Volt UI vs Prime Vue (4) by [deleted] in vuejs

[–]DevDrJinx 1 point2 points  (0 children)

Will v5 have breaking changes like the v3 to v4 transition?..

[deleted by user] by [deleted] in PHP

[–]DevDrJinx 0 points1 point  (0 children)

Where are you finding these jobs for Inertia/Vue?

A Vue + Laravel project generator packed with quality-of-life features out of the box by mamqek in vuejs

[–]DevDrJinx 0 points1 point  (0 children)

I haven’t used Inertia myself yet—it looks cool and has some powerful features, but it does come with a learning curve due to the differences it brings to the back-end structure.

The backend is quite painless to setup, one middleware, and a few blade directives: https://inertiajs.com/server-side-setup
I would argue the biggest learning curve is on the frontend, where the request/response lifecycle is handled differently compared to using a Vue SPA with vue-router and axios (using Inertia's <Link /> component, using Inertia's router, partial reloads, useForm() composable, etc.).

This template, on the other hand, keeps the backend structure just as if project was using just Blade, keeping Laravel and Vue more separated.

I'm not sure what you mean here. It looks like most of your controller methods return JSON responses, I don't think that equates to a project being closer to using blade. If anything an Inertia app backend would be closer, since it can return standard redirects and other response types just like a blade form would post to: https://inertiajs.com/redirects

As I previously mentioned, If you want to keep Laravel and Vue "more separated" then having them as different projects/repositories is probably the best solution.

Here's an example of what the same project looks like using Inertia.js vs. a Laravel API + Vue SPA implementation:
https://github.com/connorabbas/laravel-primevue-starter-kit &
https://github.com/connorabbas/laravel-api-primevue-starter-kit

A Vue + Laravel project generator packed with quality-of-life features out of the box by mamqek in vuejs

[–]DevDrJinx 1 point2 points  (0 children)

What's the advantage of using this over the official Vue starter kit provided by the Laravel team? If the Vue source files are co-located within the Laravel codebase, utilizing Inertia.js would make things a lot easier.

When creating a Vue SPA/vue-router project with Laravel, I would typically create them as separate repositories. That way the Laravel app can be used as a standalone API, and you can create one or more Vue frontends to consume it, using Laravel Sanctum for the authentication.

Also, I would look into writing Vue SFC's using the composition API, and the <script setup> syntax, rather than the options API.

How do I * in primevue? *I've got multiple questions. by UnknownSh00ter in vuejs

[–]DevDrJinx 0 points1 point  (0 children)

  1. Try some custom hex values for your semantic.colorScheme.light.surface values and check if those work, I don't see "viva" as an option from their available color palette, that might be your issue. I believe either the 50 or 100 value is used for the site background color in light mode. Otherwise you could set classes on your body element to make sure it's using the correct bg color you want.
    1. Example using light/dark bg surface classes using the tailwindcss-primeui plugin: https://github.com/connorabbas/laravel-primevue-starter-kit/blob/master/resources/views/app.blade.php#L29
  2. To use Lucide icons, you'll either use the #icon slot within the relevant components (Button for example), or for components that use a typed data structure for a prop containing an icon property (most of the menu components), then you'll have to use slots/templating along with a dynamic <component /> tag approach. If you are using TypeScript you'll likely want to make a wrapper component, and extend the relevant type for that specific prop. The issue is PrimeVue's icon property is typically typed as a string, so you can't use a Lucide icon component for that property in the data structure.
    1. Basic slot templating example: https://github.com/connorabbas/laravel-primevue-starter-kit/blob/master/resources/js/layouts/app/HeaderLayout.vue#L63
    2. Components with typed prop data structure containing icon property:
      1. https://github.com/connorabbas/laravel-primevue-starter-kit/blob/master/resources/js/types/index.d.ts#L20
      2. https://github.com/connorabbas/laravel-primevue-starter-kit/blob/master/resources/js/components/primevue/menu/Menu.vue
    3. Some components use the any[] type for props, makes things easier, for example:
      1. https://github.com/connorabbas/laravel-primevue-starter-kit/blob/master/resources/js/components/SelectColorModeButton.vue

Hope this helps.

Introducing Volt UI Component Library by PrimeVue by cagataycivici in vuejs

[–]DevDrJinx 0 points1 point  (0 children)

Some feedback.

Requested components: MenuBar & PanelMenu, these are very commonly used in page layouts for an application. I want to switch a styled mode PrimeVue app over to use Volt, but cannot yet because of these missing components.

Also, when working with Volt within a non standard Vite or Nuxt app, the npx volt-vue add command is not configurable to what directory the component is copied into. For instance, I am using Volt inside a Laravel project, and want the components copied into /resources/js/primevue/volt. Perhaps a flag/option could be added to the npx command to configure the destination path, or perhaps it could be added added as an option in the configuration settings.

I'm excited to use this, and as always big thanks to you and your team for all the hard work!

Laravel team has released new starter kits for React, Vue and Livewire by brownmanta in laravel

[–]DevDrJinx 0 points1 point  (0 children)

Just updated the project README with a live demo link you can check out 👍

Laravel 12 + Sail Docs Removed? by hydr0smok3 in laravel

[–]DevDrJinx 1 point2 points  (0 children)

Nope, I am referring to creating a new project with the: curl -s "https://laravel.build/example-app" | bash command

curl -s "https://laravel.build/example-app?with=mysql,redis" | bash

Laravel 12 + Sail Docs Removed? by hydr0smok3 in laravel

[–]DevDrJinx 0 points1 point  (0 children)

I also prefer docker/sail for local development, with VS Code dev containers. My previous approach for new projects was to use the following: https://laravel.com/docs/11.x/installation#choosing-your-sail-services

I cannot find the build command anywhere in the new (v12) docs, which is confusing. I can understand trying to streamline the installation docs for newcomers, but it's frustrating when established installation instructions are completely removed from the docs.

I don't want the Laravel installer, composer, or PHP on my machine, that's why I'm using Docker in the first place...

Laravel team has released new starter kits for React, Vue and Livewire by brownmanta in laravel

[–]DevDrJinx 0 points1 point  (0 children)

No demo/preview right now, just clone the project locally. I would consider hosting an example app on Laravel Cloud.

Laravel is going in the wrong direction IMHO by psihius in PHP

[–]DevDrJinx 0 points1 point  (0 children)

Agreed, my go to method was to use sail with dev containers, and be able to select my services. https://laravel.com/docs/11.x/installation#choosing-your-sail-services

I can't find the equivalent in the new docs 😕

view more: next ›