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

Switch to using projen for each package tested #899

Open
moltar opened this issue Jul 5, 2022 · 2 comments
Open

Switch to using projen for each package tested #899

moltar opened this issue Jul 5, 2022 · 2 comments

Comments

@moltar
Copy link
Owner

moltar commented Jul 5, 2022

Using projen would open up the possibility of having different configs for each package that is being tested.

This would be necessary for #898, but we have also ran into this with spectypes (#856).

@johannes-lindgren
Copy link
Contributor

johannes-lindgren commented Oct 12, 2024

When trying to add a new benchmark, I noticed that I couldn't use package.json "exports". It was difficult to fix because a change in project configuration would also affect other benchmarks. Maybe this issue would help solving that.

@moltar
Copy link
Owner Author

moltar commented Oct 12, 2024

@johannes-lindgren What was the use case for exports?

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

2 participants