franciscokloganb / vitesse-enterprise Goto Github PK

Description

As a user
I want to be reassured that my package.json#build script is also a production build and that package.json#build:prod is an alternative that adds compilation for server side rendering
so I can use either one without bias or fear of loss of performance.

Acceptance criteria

Scenario user reads package.json
Given a set of scripts
Then the build method should be named build:prod
And the build:prod method should be named build:prod:ssr

Additional notes

Files that depend on this scripts, e.g.: README, CI/CD files and, others, might need to be updated.

Context (Environment)

When in Gitlab pipeline component-tests seem to initiate but then are stuck at the start of the process, eventually, timing out after 15 minutes. Consequently the pipeline is currently only executing e2e-tests.

Expected Behavior

It would be expected for Component tests to run smoothly on the GitLab CI/CD pipeline just as they do on GitHub Actions.

Current Behavior

Component tests do not execute. Tried multiple methods and none seemed to work.

Steps to Reproduce

1. Import this public repository onto your GitLab account
2. Go to the project's dashboard and open the new project
3. On the project menu, select CI/CD > Editor, make and commit a change
4. See how the pipeline gets stuck when trying to run component tests

Possible Solution

Do not know any but the Yarn implementation seen in this repository seems to work: https://github.com/Uninen/vite-ts-tailwind-starter/blob/main/.gitlab-ci.yml

Context (Environment)

I set a base url prefix in vite.config.ts

export default defineConfig({
  base: '/test/',
  ...
})

I ran pnpm dev but the page http://localhost:4000/test/ is a 404 not found
I can't access to the page until I hard reload (cmd + maj + R) the page.
Same for hot-reload, after each I'm redirecting to the 404 page, and I have to hard reload.

Hey,

Well done on on setting up an enterprise structure; this is similar to how I build my projects too.

I see in your "nice to haves" you mentioned folder aliasing. You might want to consider Alias HQ (one of mine) to expand on this.

You set up your aliases once only in tsconfig.json then choose an integration for each toolchain, for example Vite:

import { defineConfig } from 'vite'
import hq from 'alias-hq'

export default defineConfig({
  resolve: {
    alias: hq.get('rollup')
  }
})

Anyway. Hope that's helpful.

Great work @FranciscoKloganB!

I need to do 2 different builds for my current project (from the same codebase). Each build is just a different combination of modules. Do you have any suggestions on the best way to set that up?

Thanks in advance

Description

This is feature what allow us to code without ide

Thanks for sharing this template. We're finding it very helpful.

There have been a couple of updates to vitesse in the last year. Would you be able to add them?

• Add unplug-vue-macros packlage. See: https://github.com/antfu/vitesse/blob/75e627165659d615148a69fa2f43156e23f34ab8/package.json#L52 and https://vue-macros.sxzz.moe/
• Add vite-plugin-vue-component-preview package. See: https://github.com/antfu/vitesse/blob/75e627165659d615148a69fa2f43156e23f34ab8/package.json#L57
• Add starter Dockerfile. See: https://github.com/antfu/vitesse/blob/main/Dockerfile

I think that's all the changes... I may have missed something though