Hello! Windows: 11 Node: 16.20 Npm: 8.19 In console i see error: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

I was trying to build some templates with the command vituum build , but every time, the views folder from the output directory was been deleted. It was until I tried the command vituum headless that finally the views folder wasn't deleted.

We have a couple of (example data) JSON files within our project (/data/categories.json etc.), which are requested and processed from the front-end. Those should not be processed by the template engines and only be served by the server when called from the front-end.

Right now those get processed by vituum and lead to errors like this one:

Error: ENOENT: no such file or directory, open '/abcdef/src/views/data/categories.json.html'
    at Object.openSync (node:fs:599:3)
    at Object.readFileSync (node:fs:467:35)
    at file:///abcdef/node_modules/vituum/plugins/middleware.js:48:142 

What's the approach here? Is there a setting to exclude certain files? Should I change the project structure somehow?

Cheers

Hi!

I have configured vituum. At the moment, when the project is being built (npm run build), the pug pages from src/views/ are going to dist/views/ How can I change the path during assembly so that pug pages are assembled in dist/ (without the views folder, that is, in the dist folder itself)

My repository with my configuration: vituum-gulp-template

After altering our existing Vite project to Vituum the HMR error message overlay only flashes briefly in the browser before disappearing.

Restarting vite will render the error message once, after a browser refresh or a refresh because of a file change the error message will only flash briefly again.

Any ideas what could cause this behaviour?

Cheers

When building the project, the files are collected in the public folder, while the build.outDir parameter is ignored.

vite.config.js:

import { defineConfig } from 'vituum';
import twig from '@vituum/twig';

export default defineConfig({
  integrations: [twig()],
  templates: {
    format: 'twig',
  },
  build: {
    outDir: '../dist',
  },
});

The build.rollupOptions.output option also doesn't work.

vite.config.js:

// ...
export default defineConfig({
  // ...
  build: {
    // ...
    rollupOptions: {
      output: {
        entryFileNames: `assets/js/[name].js`,
        chunkFileNames: `assets/js/[name].js`,
        assetFileNames: `assets/[name].[ext]`
      }
    }
  }
});

The test was carried out both on a local Linux machine and in a stackblitz environment.

Hi,

Thank you for this great tool! It makes it super easy to use and configure handlebars and nunjucks templates in my vite projects. I was wondering if you had any advice regarding integration with storybook's vite builder. I have use webpack and handlebars-loader webpack plugin https://github.com/pcardune/handlebars-loader to load .hbs templates inside component.stories.js storybook files in the past... I don't have a lot of experience with Vite so I am not sure how to go about it, since when I try to import an .hbs template inside a js file I get the following error:

Internal server error: Failed to parse source for import analysis because the content contains invalid JS syntax. You may need to install appropriate plugins to handle the .hbs file format, or if it's an asset, add "**/*.hbs" toassetsIncludein your configuration.

any advice on how to get it working would be greatly appreciated.

thank you

Is there any chance Vituum could provide a functionality similar to what handlebars-loader does when using its partialDirs option in order to use any partial without the need of specifying it's relative path? Not sure what would be the best approach to get it working.

Thank you in advance for any info you can provide regarding this question.