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

Compatibility with yarn 2 (or yarn 1 PnP mode) #458

Open
Tracked by #933
xaviergonz opened this issue Jan 25, 2020 · 11 comments
Open
Tracked by #933

Compatibility with yarn 2 (or yarn 1 PnP mode) #458

xaviergonz opened this issue Jan 25, 2020 · 11 comments
Labels
kind: feature New feature or request PR welcome scope: integration Related to an integration, not necessarily to core (but could influence core)

Comments

@xaviergonz
Copy link

Current Behavior

Yarn v2 got a stable release today, and it uses PnP (instead of node_modules) exclusively
Right now tsdx test, tsdx build (and maybe others) have some issues with it (specially with finding the typescript package if it is not globally installed, which would be my case).

Desired Behavior

TSDX should work out of the box with yarn v2 / yarn v1 PnP mode

Suggested Solution

Fix TSDX build configurations / upgrade build packages.

Who does this impact? Who is this for?

People who use yarn v1 PNP mode and/or yarn v2.

Describe alternatives you've considered

N/A

@jaredpalmer
Copy link
Owner

jaredpalmer commented Jan 25, 2020 via email

@xaviergonz
Copy link
Author

Such as this one? https://github.com/arcanis/rollup-plugin-pnp-resolve

@jaredpalmer
Copy link
Owner

Gonna press pause until this is sorted out: yarnpkg/berry#766 (comment)

@agilgur5 agilgur5 added kind: feature New feature or request scope: integration Related to an integration, not necessarily to core (but could influence core) labels Mar 20, 2020
@kylemh
Copy link
Contributor

kylemh commented Apr 5, 2020

It looks like it's been sorted. What're we thinkin on this? It will actually help with #122 a bit because Yarn2 will topologically sort packages for the correct build order before tests (for example). The alternative on v1 is to manually define the correct order 😭

@agilgur5
Copy link
Collaborator

agilgur5 commented Apr 7, 2020

I'll mark this as PR welcome. node_modules is referenced in a few places and I know some of our dependencies rely on it too, so I don't think the amount of work for this is trivial. We'd also have to support both versions too, not just Berry. And probably run tests against both versions in CI too.

Not really a high priority given amount of work, other priorities, and that the community hasn't really moved on to Berry as a whole (including little interest in this issue and the fact that it's not the default version).

@timini
Copy link

timini commented Nov 2, 2020

can i leave a bounty?

@timini
Copy link

timini commented Nov 20, 2020

is there any direction / roadmap for someone who wanted to get started with this?

@jaredpalmer
Copy link
Owner

@timini is there a bounty service you recommend?

@kylemh
Copy link
Contributor

kylemh commented Nov 20, 2020

https://issuehunt.io/

@merceyz merceyz mentioned this issue Nov 24, 2020
6 tasks
@timini
Copy link

timini commented Mar 16, 2021

can a repository owner sign up and add this repo to issue hunt please?

https://issuehunt.io/r/new

@hoop71
Copy link

hoop71 commented Dec 24, 2021

This would be a great improvement! The Release Workflow feature of Yarn 2 makes a lot of sense for TSDX!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: feature New feature or request PR welcome scope: integration Related to an integration, not necessarily to core (but could influence core)
Projects
None yet
Development

No branches or pull requests

6 participants