Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--output-path doesn't allow for absolute paths #187

Closed
TheDevMinerTV opened this issue Feb 12, 2024 · 0 comments
Closed

--output-path doesn't allow for absolute paths #187

TheDevMinerTV opened this issue Feb 12, 2024 · 0 comments

Comments

@TheDevMinerTV
Copy link

TheDevMinerTV commented Feb 12, 2024

Describe the bug

When passing the output path to either of the binaries, the files will end up in the current directory joined with the passed in path instead of using the output path as an absolute value.

Reproduction

  1. Run npx @unlighthouse/cli --build-static --output-path /tmp/unlighthouse0123456789 --site https://devminer.xyz
  2. Check your /tmp folder, the files won't be there
  3. Check ./tmp and they'll be there instead

ℹ️ The output will also show the wrong path [Unlighthouse] ✔ Static report is ready for uploading: ./tmp/unlighthouse0123456789 (notice the .)

System / Nuxt Info

System:
    OS: Linux 6.5 Alpine Linux
    CPU: (48) x64 Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
    Memory: 62.12 GB / 204.49 GB
    Container: Yes
    Shell: 1.36.1 - /bin/ash
  Binaries:
    Node: 20.11.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.4 - /usr/local/bin/npm
  Browsers:
    Chromium: 121.0.6167.8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant