Skip to content

Reverts #39277 removing bundledPackageName - #41499

Merged
Orta Therox (orta) merged 4 commits into
microsoft:masterfrom
orta:removeBundlePackage
Jan 8, 2021
Merged

Reverts #39277 removing bundledPackageName#41499
Orta Therox (orta) merged 4 commits into
microsoft:masterfrom
orta:removeBundlePackage

Conversation

@orta

@orta Orta Therox (orta) commented Nov 11, 2020

Copy link
Copy Markdown
Contributor

Re: #39277 - note that there is #41510 which instead turns this into a suggestion instead of a compiler error.

It's looking like we don't want to ship 4.1 with bundledPackageName included as-is, this PR reverts those changes and tests.

@orta Orta Therox (orta) self-assigned this Nov 11, 2020
@typescript-bot TypeScript Bot (typescript-bot) added Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug labels Nov 11, 2020
@orta Orta Therox (orta) changed the title Reverts #39277 Reverts #39277 removing bundledPackageName Nov 11, 2020
@weswigham

Wesley Wigham (weswigham) commented Nov 11, 2020

Copy link
Copy Markdown
Member

Orta Therox (@orta) rather than reverting the whole thing, why not just remove the new error on program construction if the break is too undesirable... (or, better yet, convert it to a suggestion diagnostic somehow rather than removing it outright)? The flag definitely allows you to get better declaration file output.

@orta

Copy link
Copy Markdown
Contributor Author

Yeah, I'm totally open to this instead. Does that work for you Daniel Rosenwasser (@DanielRosenwasser) / Ryan Cavanaugh (@RyanCavanaugh)?

Will take a fresh stab at that tomorrow 👍🏻

@orta

Orta Therox (orta) commented Nov 12, 2020

Copy link
Copy Markdown
Contributor Author

I'll make a PR to release-4.1 cherry-picking either this PR or #41510 when one is merged

@DanielRosenwasser

Copy link
Copy Markdown
Member

Even if we want to keep the feature, I'm not sold on the name and there isn't much time to bikeshed that.

TypeScript Bot (@typescript-bot) cherry-pick this to release-4.1

@typescript-bot

TypeScript Bot (typescript-bot) commented Nov 12, 2020

Copy link
Copy Markdown
Contributor

Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to run the task to cherry-pick this into release-4.1 on this PR at 0c00853. You can monitor the build here.

@typescript-bot

Copy link
Copy Markdown
Contributor

Hey Daniel Rosenwasser (@DanielRosenwasser), I couldn't open a PR with the cherry-pick. (You can check the log here). You may need to squash and pick this PR into release-4.1 manually.

@weswigham

Copy link
Copy Markdown
Member

Even if we want to keep the feature, I'm not sold on the name and there isn't much time to bikeshed that.

Whoa, we've had the flag shipped in the whole beta process - we've already bikeshedded the name. Removing just the error is way less disruptive than stripping the whole feature, and lower risk to the release as a whole.

@sandersn

Copy link
Copy Markdown
Member

Orta Therox (@orta) Since #41510 is less disruptive, do you want to keep this PR around?

@orta

Copy link
Copy Markdown
Contributor Author

When this came up in a design meeting, the consensus was still to remove this option, but I'd like to give it one last discussion before dropping completely.

@orta

Copy link
Copy Markdown
Contributor Author

OK, dropping this flag from 4.2 also.

@orta
Orta Therox (orta) merged commit 055f363 into microsoft:master Jan 8, 2021
Zzzen (Zzzen) pushed a commit to Zzzen/TypeScript that referenced this pull request Jan 16, 2021
* Reverts microsoft#39277

* Bring back modeyule resolution for the test runner
@menduz

menduz commented Jan 19, 2021

Copy link
Copy Markdown

Oh no! Decentraland was really relying on this feature.

Help me with the planning for our tooling: is this completely removed from the plans or it is a temporary thing?

Thanks

@weswigham

Copy link
Copy Markdown
Member

We have plans to bring it back, but with a different name, and without the error requiring its use - some contention was had that the name bundledPackageName potentially implied that we were some kind of full service bundler, rather than a relatively dumb concatenator.

@arose

Copy link
Copy Markdown

We have plans to bring it back, but with a different name, and without the error requiring its us

Any update on this?

@microsoft Microsoft (microsoft) locked as resolved and limited conversation to collaborators Oct 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

7 participants