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

fix(node): some directory separators are still inconsistent between platforms in tasks.json and package.json #3406

Merged
merged 2 commits into from
Feb 28, 2024

Conversation

gmeligio
Copy link
Contributor

@gmeligio gmeligio commented Feb 27, 2024

Related to #3284 (comment)

This is the second attempt at fixing the directory separator issue for lambda entrypoints, which was started in #3387.

I tried adding unit tests for renderBundleName. Unfortunately, this can't be unit-tested now because NodeJS exports the path package for the Linux platform instead of Windows at import time and not at runtime.
https://github.com/nodejs/node/blob/f28ccd3941e70a825786eff7e28f59014ac76ac9/lib/path.js#L1546

I tested it locally in an example project, and it looks like it's fixed now.
image


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

… tasks.json and package.json, second attempt
@gmeligio gmeligio marked this pull request as ready for review February 27, 2024 19:23
@mrgrain mrgrain changed the title fix(node): directory separators are inconsistent between platforms in tasks.json and package.json, second attempt fix(node): some directory separators are still inconsistent between platforms in tasks.json and package.json Feb 28, 2024
@mrgrain
Copy link
Contributor

mrgrain commented Feb 28, 2024

@gmeligio I assume this would be tested automatically once we start running builds on Windows?

@mergify mergify bot merged commit 49a51ef into projen:main Feb 28, 2024
14 checks passed
@mrgrain
Copy link
Contributor

mrgrain commented Feb 28, 2024

@gmeligio For some reason this broke the release: https://github.com/projen/projen/actions/runs/8079532064/job/22074128464#step:6:1035

Are you around to fix this forward? Otherwise I'll just revert the PR and we can try again.

@gmeligio
Copy link
Contributor Author

Sorry. Haven't had the time to look at it. I'll look into it in an hour or so. Go ahead and revert if necessary.

@mrgrain
Copy link
Contributor

mrgrain commented Feb 28, 2024

No worries, turns out it got fixed via #3409

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

Successfully merging this pull request may close these issues.

None yet

2 participants