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.

Sign up for GitHub

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

Jump to bottom

Use Bun for dependency management #22

Open
PaulRBerg opened this issue Dec 31, 2023 · 1 comment
Open

Use Bun for dependency management #22

PaulRBerg opened this issue Dec 31, 2023 · 1 comment
Labels
effort: high Large or difficult task. priority: 2 We will do our best to deal with this. type: build Changes that affect the build system or external dependencies. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.

Comments

@PaulRBerg
Copy link
Member

Refs:
@PaulRBerg PaulRBerg mentioned this issue Dec 31, 2023
Closed
@PaulRBerg PaulRBerg added effort: high Large or difficult task. priority: 1 This is important. It should be dealt with shortly. type: build Changes that affect the build system or external dependencies. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise. and removed dependencies labels Jan 1, 2024
@razgraf razgraf added priority: 2 We will do our best to deal with this. and removed priority: 1 This is important. It should be dealt with shortly. labels Feb 15, 2024
@razgraf
Copy link
Member

razgraf commented Feb 15, 2024

This isn't possible at the moment as the repository currently uses two package managers: Envio needs pnpm, the subgraphs are built using yarn.

I've tried updating to pnpm at some point but the subgraph projects weren't very happy about it (something to do with the extended tsconfig).

As soon as Envio starts supporting bun we can circle back to this issue. It's important we use only one package manager so we can refactor the codebase to promote re-usability between subgraphs and indexers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: high Large or difficult task. priority: 2 We will do our best to deal with this. type: build Changes that affect the build system or external dependencies. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PaulRBerg @razgraf