wtchnm / vitamin Goto Github PK

Hi, would you guys be willing to add a state management library like Redux?
I'm currently trying to do this, but I'm still new to React, so I don't know what's the best practice to add it...

is there a benefit to making this be pnpm?

afaik, it being set to yarn is probably benign; but just wanted to call it out in case it helps.

eslint.packageManager: controls the package manager to be used to resolve the ESLint library. This has only an influence if the ESLint library is resolved globally. Valid values are "npm" or "yarn" or "pnpm".
https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint

see also:

• 3fc261c

Hi! I'm trying to use this template to setup a monorepo with pnpm workspaces (or nx?). It should look like:

___ frontend (vite)
   |_ services
   |  |_ service 1 ([nest](https://nestjs.com/) service)
   |  |_ service 2 ([nest](https://nestjs.com/) service)
   |_ tools (shared types, tools and/or components, as in: eslint-plugins, cli tools, etc.)

I know it's not that complicated, it's laborious, as in: hoist some devdeps, hoist cypress, and other stuff, but if there's any chance you guys have already a branch or any guidance on this? thanks!!!

Hi folks,

This is an awesome template and I am very enjoy it. But I found there are some dependencies which are not the latest ones under this template, and some configuration files are also using legacy settings/formats.

I very much wish I could use the new features brought from latest version of dependencies when I start a new project, so can you guys check and update these things?

For example:

How can support Access-Control-Allow-Origin?

Hello, first of all thanks for this nice template.

I've just downloaded this template, and I am facing an ESLint issue in the cypress folder files. (src files are correctly linted)
I am using WebStorm as my IDE.

Hi, we've been using the Vitamin starter and everything worked great in the beginning :)

But at some point as the project grew, we occasionally had builds that would break completely with this error:

It was quite harder debugging as it only happens once in a while, but more frequently when building through our CI pipeline.
We finally found that disabling these lines used in this starter would stop the errors:

Not sure if this is only specific to our use case and combination of dependencies, but I wanted to flag it here in case other people had the same problem. I'm also curious why optimizeDeps was disabled in the first place?

When adding a new font, the value of the default config should still be used.

Right now the code is: sans: ['Inter', defaultConfig.theme.fontFamily.sans].

But as stated here https://estevanmaito.me/blog/how-to-add-custom-fonts-to-tailwind-css#extending-fontfamily, a better way would be to do:
sans: ['Inter', ...defaultConfig.theme.fontFamily.sans].

This way the values of the defaultConfig will be applied.