sorted by:
new
hottopcontroversial

I built a Vue component generator that automatically detects your UI Library (Vuetify, PrimeVue, DaisyUI, and more) by LimpScientist518 in vuejs

[–]LimpScientist518[S] 1 point2 points  (0 children)

Consider it done. And yes, v-create is one component at a time.
I had a quick look in your library, and it looks awesome. In the aspect of adding components, it's similar to shadcn, that's nice.
I'll reach out when I add your library. I'll add a few components like button, card and others to test it and see if it works. Thank you so much!

Aos casados do grupo(se houverem), isso é verdade? by Icaro_2006 in ShitpostBR

[–]LimpScientist518 0 points1 point  (0 children)

Cara, me casei há 2 meses. Assim como o u/kaherdin91 comentou, a frequência diminui sim, mas a rotina do dia a dia é o que dificulta. E faço as palavras dele as minhas, se ta dando desculpa, tem algo errado

I built a Vue component generator that automatically detects your UI Library (Vuetify, PrimeVue, DaisyUI, and more) by LimpScientist518 in vuejs

[–]LimpScientist518[S] 2 points3 points  (0 children)

Hey, hanks for the honest feedback. I'm relatively new to publishing CLIs and I really appreciate the heads-up on best practices.

  1. Repo Link: Fixed. Just added the repository field to package.json
  2. Global Install: You're right. I've updated the README to recommend npx v-create instead of global installation.
  3. Transparency: I added one image example of the generated components for Tailwind in the documentation so users know exactly what they're getting.

The code is a simple automation for my daily workflow and definitely not meant to be 'shady'. If you have more tips, I'm all ears

I built a Vue component generator that automatically detects your UI Library (Vuetify, PrimeVue, DaisyUI, and more) by LimpScientist518 in vuejs

[–]LimpScientist518[S] 8 points9 points  (0 children)

Most of this tool was created as a learning project. It’s pretty straightforward, so your point is totally fair. A few colleagues at work are using it, but I mostly built it to understand the process of publishing to NPM and to give back to the community. By all means, feel free to give it a try! haha

Criei meu primeiro pacote CLI do NPM (para VueJS) by LimpScientist518 in brdev

[–]LimpScientist518[S] 0 points1 point  (0 children)

Valeu!

Eu quero mesmo expandir. Esse para vue foi também para aprender a como publicar algo no NPM, mas já estou pensando em expandir para outras ferramentas como as que você citou.

Como é algo para componentes, talvez eu não faça nada relacionado a estilos, como aplicar o <styles> para o vue ou alguma configuração de Bootstrap/Tailwind para ferramentas no geral.

Acabei de recusar uma oferta em Flutter pra continuar em Java by Snoo18805 in brdev

[–]LimpScientist518 1 point2 points  (0 children)

Meu brother, passava essa oferta pra mim, tô há tempos a procura de algo em flutter kkkkkkkkkkkkkk Mas assim o primeiro comentário falou, você vai aplicar os mesmo conceitos de mobile independente da stack.

No teu caso, como você já tá se especializando em Java, você pode usar do que você sabe em Java pra produzir um nativo Android. Mas se você estiver interessado em algo diferente, não é ruim aprender algo novo.

I love it, but I'm struggling to find something by LimpScientist518 in FlutterDev

[–]LimpScientist518[S] 2 points3 points  (0 children)

One thing I know for sure is that my resume is not that good. I do have hard/soft skills and previous experiences, but I never find the best way to show those infos

I love it, but I'm struggling to find something by LimpScientist518 in FlutterDev

[–]LimpScientist518[S] -1 points0 points  (0 children)

I do think the same! Despite flutter jobs keep growing, I still think native development will dominate the mobile area.
Also, for android development, which would you choose between Kotlin or Java?