fix: issue with absolute output paths #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
maybe it fix also similar issue: #36
What is the purpose of this pull request?
Description
Use
resolve
thanjoin
to computefullFilePath
to handleoutputPath
correctly if set to an absolute path.Resolve is checking if a parameter is an absolute path and ignore preceding paths.
Join always concatenate all path parameters which add an base path to the outputPath - that creates a non-existing path if outputPath is already absolute.
Checks
fixes #number
pnpm lint && pnpm build
Additional Context
I use vite with absolute output paths to generate builds.