-
Notifications
You must be signed in to change notification settings - Fork 24.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Summary: Removes code that is no longer used Reviewed By: matryoshcow Differential Revision: D4021932 fbshipit-source-id: d73dc8450478288afd71eab451a30a505e7de945
- Loading branch information
1 parent
4d0b3e6
commit 7762f37
Showing
1 changed file
with
0 additions
and
46 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7762f37
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi there,
I am wondering why these methods were removed from packager. This is a public API documented in react-packager that we were using and pruning them in this fashion is not the best engineering practice. Can this be restored / can I resubmit a revert for this?
Thanks
Ashish
7762f37
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, sorry for breaking you. Could you tell me how you are using these functions? I didn’t even realise we have this sub-README lying around until now.
Packager will go through a lot of changes in the next months, and I need to be aware of what people are using.
7762f37
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi there,
Thanks for quick reply. We have a gulpfile that creates packages based off our config and it goes through some custom logic that I cannot disclose. We then bind several scripts together using commonJS techniques at runtime. Providing an API for building bundles therefore is essential for our project.
Thanks
Ashish
7762f37
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also can you list at high level changes we can expect in the packager thats in the pipeline.
Thanks
7762f37
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are reorganising and rewriting a lot in the core – we can keep these APIs though if they are used. Are you using all of them, or only specific ones?
7762f37
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly I am just using buildBundleFromUrl. However at the time I started it was the only method available. Diff above shows a whole lot of similar methods that is highly confusing. So if you can provide an equivalent of buildBundleFromUrl or buildPrepackBundle it would be sufficient.
7762f37
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I will do that