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

Fix: Angular no longer has issues with plugins that aren't named "nativescript" #9172

Merged
merged 1 commit into from Jan 26, 2021

Conversation

NathanaelA
Copy link
Contributor

PR Checklist

  • The PR title follows our guidelines:
  • You have signed the CLA.
  • All existing tests are passing:

What is the current behavior?

When webpacking in Angular; it requires the plugins to have the name "nativescript", "@NativeScript", "tns" somewhere in it. If it doesn't have it -- it will not consider it a plugin to do any .ios. / .android. file renaming causing the build to fail.

What is the new behavior?

Makes angular be consistent with all the other flavors, and now does NOT care about the package name in its check to see if it is a file it needs to rename.

It does add about between a -10% to a +5% slowdown to just the WebPack portion of the build depending on the size of the application. (No other speed or size impacts) In smaller apps; the webpacking is now faster. In apps that take about 30 seconds for just the webpacking, it adds an additional second.

@cla-bot cla-bot bot added the cla: yes label Jan 26, 2021
@NathanWalker NathanWalker merged commit 79a5fc8 into master Jan 26, 2021
@NathanWalker NathanWalker deleted the angular_webpack branch January 26, 2021 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants