Path Resolving

[Rados51]

It would be cool if we could pass alias object in the same way as define (ladleConfig.define).
Many of my projects depends on path resolving, as I can easily access nested files across project.

If I am not mistaken, the first code block should work just fine, but I've added a second solution as I don't work Vite quite often.
I would try to make a pull request, but I am not sure how to test/load Ladle from the local folder (as yarn add "/path-to-folder" does not work as I thought).

I guess you could add it just to https://github.com/tajo/ladle/blob/master/packages/ladle/lib/cli/vite-base.js and few other places that use ladleConfig.

// https://theroadtoenterprise.com/blog/how-to-set-up-path-resolving-in-vite
// vite.config.js
import { defineConfig } from 'vite';
import path from 'path';

export default defineConfig({
  plugins: [],
  resolve: {
    alias: {
      '@': path.resolve(__dirname, './src'),
      '@plugins': path.resolve(__dirname, './src/plugins'),
    },
  },
});

// https://stackoverflow.com/questions/68217795/vite-resolve-alias-how-to-resolve-paths
// vite.config.js
import { defineConfig } from 'vite';
import path from 'path';

export default defineConfig({
  resolve: {
    alias: [
      { find: '@', replacement: path.resolve(__dirname, './src') },
      { find: '@plugins', replacement: path.resolve(__dirname, './src/plugins') },
    ]
  }
});

[tajo]

Yea, I'm going to expose alias parameter. Is it common to use @ as an alias for src since someone else mentioned that too. If so, it could be a default.

[tajo]

Fixed #55

With version 0.8.3, you can now create .ladle/config.mjs and add custom import aliases:

export default {
  resolve: {
    alias: {
      "@": "../src",
    },
  },
};