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

feat: move gt3 library #3641

Merged
merged 9 commits into from
Dec 7, 2023
Merged

feat: move gt3 library #3641

merged 9 commits into from
Dec 7, 2023

Conversation

dolcalmi
Copy link
Collaborator

@dolcalmi dolcalmi commented Dec 1, 2023

nicolasburtey
nicolasburtey previously approved these changes Dec 1, 2023
@nicolasburtey
Copy link
Member

(tests are not passing)

@@ -176,6 +180,10 @@ build_node_modules = rule(
default = False,
doc = "Only install production dependencies"
),
"local_packages": attrs.string(
default = "lib",
Copy link
Contributor

@vindard vindard Dec 4, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bodymindarts to accommodate locally vendored npm packages I changed the build_node_modules.py code to also copy those vendored files during the turbo install process.

I know we had originally decided that we want to use the top-level lib folder for common configs across sub-projects. Is this where we also want to store vendored npm packages (like was introduced here), or is there another folder that we'd prefer, maybe third-party?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if lib it is a folder for common configs then is not a good name, also, tracing-rs does not look like a common config but a library

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lib is a folder for shared libraries....

Some shared libraries may contain common config (that is imported as a library).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

si uses their lib folder for all shared libraries so I think you're right, this is the right approach here
https://github.com/systeminit/si/tree/main/lib

@vindard vindard force-pushed the feat-move-gt3-library branch from d4916b7 to e280a12 Compare December 4, 2023 16:35
nicolasburtey
nicolasburtey previously approved these changes Dec 6, 2023
@vindard vindard dismissed nicolasburtey’s stale review December 6, 2023 14:09

We hae some changes to make to the level we're bringing in vendored libs at in the the build process

dolcalmi and others added 4 commits December 6, 2023 11:45
During turbo prune, turbo brings in the necessary local package dirs,
and figures out the pruned package.json needed. We would need to also
bring along the package dependency js files somehow which turbo doesn't
seem to handle internally for local packages.

This PR is to explitly copy these local package files across during the
build_node_modules step after turbo prune.

Future improvements:
- figure how to simply do this directly with turbo and local packages
@dolcalmi dolcalmi force-pushed the feat-move-gt3-library branch from e280a12 to b3d209c Compare December 6, 2023 16:47
@vindard
Copy link
Contributor

vindard commented Dec 6, 2023

Toolchain specific changes: 6c14818...feat-move-gt3-library

@bodymindarts
Copy link
Member

Looks like its still failing:

 Cannot find module '@galoy/gt3-server-node-express-sdk' from 'src/services/geetest.ts'

@dolcalmi dolcalmi merged commit c4bc99b into main Dec 7, 2023
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants