Custom build command

[xxSkyy]

Hi, on one of my low memory vps building with vite throws Allocation failed - JavaScript heap out of memory error, to fix it I need to add NODE_OPTIONS=--max-old-space-size=4000 and run it before rails assets:precompile.

Are there option to customize build command on assets:precompile with properties like NODE_OPTIONS= >

[ElMassimo]

Hi Sky! @xxSkyy

Setting the NODE_OPTIONS environment variable to be globally available in the server that performs the assets precompilation should make it available in the Vite process as well.

An alternative would be to customize viteBinPath in your config/vite.json to use a different executable (for example, one that executes vite after setting NODE_OPTIONS).

[xxSkyy]

@xxSkyy we set it in the tailwind.config.js configuration file:

module.exports = {
  mode: 'jit',
  ...

But I've got problem with JIT exact this one
https://tailwindcss.com/docs/just-in-time-mode#styles-don-t-update-when-saving-content-files
and I need set TAILWIND_MODE , then JIT mode works well

[ElMassimo]

Try asking in the Vite.js Discord forum, there must be other users using Tailwind.

As far as the vite binary is concerned, any environment variables you provide will be passed through, so it's likely that the docs you linked to are referring to the PostCSS cli, and don't apply in this case.

I prefer Windi CSS, which is mostly compatible with Tailwind but integrates very nicely with Vite.js

Good luck!

[xxSkyy]

Try asking in the Vite.js Discord forum, there must be other users using Tailwind.

As far as the vite binary is concerned, any environment variables you provide will be passed through, so it's likely that the docs you linked to are referring to the PostCSS cli, and don't apply in this case.

I prefer Windi CSS, which is mostly compatible with Tailwind but integrates very nicely with Vite.js

Good luck!

But it's problem with vite_ruby, I can't pass anything to vite server with command, example

Vite ruby:

yarn vite --port 2222 --host

  vite v2.4.4 dev server running at:

  > Local: http://localhost:3036/vite-dev/
  > Network: use `--host` to expose

  ready in 145ms.

Normal Vite:

yarn vite --port 2222 --host

  vite v2.4.1 dev server running at:

  > Local:    http://localhost:2222/
  > Network:  http://10.0.0.51:2222/

  ready in 176ms.

[ElMassimo]

@xxSkyy The bin/vite executable is not meant to be used through yarn—use it directly as bin/vite dev.

host and port should not be passed to the CLI—configure them using config/vite.json. Else, the Ruby process will be configured differently and won't be able to connect to the Vite dev server.

---

Regardless of the above, using yarn 1.22.10 I am able to pass environment variables and CLI options, such as:

DEBUG=vite* yarn vite dev --port 2222

  vite v2.4.2 dev server running at:

  > Local: http://localhost:2222/
  > Network: use `--host` to expose

  ready in 276ms.

[ElMassimo]

@xxSkyy The problem you are experiencing with Tailwind seems related to the internal usage of the base configuration. See #115 for more details.

As a temporary workaround, you could downgrade vite to 2.3.8, it seems like the problem with base was introduced in one of the recent Vite versions.