-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
windows compatibility #226
Conversation
* @param dir target directory | ||
* @returns promise for the full path of the downloaded file | ||
*/ | ||
async function download(url: string, dir: string): Promise<string> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might seem unorthodox to implement this from scratch, but really, introducing another library was not worth it IMHO
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, mutch apreciated!
pathOfDirToExtractInArchive?: string; | ||
cacheDirPath: string; | ||
}) { | ||
const downloadHash = hash(JSON.stringify({ url, pathOfDirToExtractInArchive })).substring(0, 15); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now a bit different to your previous cachin strategy, let me know what you think of it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM in surface.
I didn't test if it actually work though...
I'll trust you on that.
var { bin } = await import(pathJoin(getProjectRoot(), "package.json")); | ||
|
||
var promises = Object.values<string>(bin).map(async scriptPath => { | ||
const fullPath = pathJoin(getProjectRoot(), scriptPath); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a bit more synchronous, eh? :)
Thank you so much for this work. |
Bummer, it dosen't work. here is an invite on for the repo so you can push on the branch: https://github.com/InseeFrLab/keycloakify/invitations |
@garronej whats broken? it worked for me and github actions were all green? |
@lordvlad I'm very very sorry 🙇🏼♂️ |
Again @lordvlad, |
haha all good. happy to make an improvement
…On Mon, Jan 30, 2023 at 1:18 AM Joseph Garrone ***@***.***> wrote:
Again @lordvlad <https://github.com/lordvlad>,
I wanted to reiterate and tell you how very sorry I am to call your PR
broken when it was I that didn’t run the right command.
Your effort is very much appreciated!
—
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJJJ2N6363G2H36Y6KMJOTWU4CGTANCNFSM6AAAAAATZWXPJY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Chown does not exist on widows. This PR uses nodejs's native fs.chmodSync instead