Skip to content
This repository was archived by the owner on Apr 8, 2020. It is now read-only.

Update NodeServices/SpaServices/NodeServices.Sockets to build using latest TypeScript and Webpack - #1748

Merged
SteveSandersonMS merged 2 commits into
masterfrom
stevesa/update-typescript-builds
Aug 30, 2018
Merged

Update NodeServices/SpaServices/NodeServices.Sockets to build using latest TypeScript and Webpack#1748
SteveSandersonMS merged 2 commits into
masterfrom
stevesa/update-typescript-builds

Conversation

@SteveSandersonMS

Copy link
Copy Markdown
Member

Previously they assumed you were using versions of TypeScript and Webpack that are by now rather outdated. This PR:

  1. Updates to the latest TypeScript/Webpack
  2. Includes package-lock.json files to lock down exactly which versions should be used, so it won't break in the future if TypeScript/Webpack themselves introduce breaking changes

@SteveSandersonMS SteveSandersonMS changed the title Update NodeServices/NodeServices.Sockets to build using latest TypeScript and Webpack Update NodeServices/SpaServices/NodeServices.Sockets to build using latest TypeScript and Webpack Aug 28, 2018

@ryanbrandenburg ryanbrandenburg left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm certainly no expert on TypeScript or WebPack, but it looks good to me.

@SteveSandersonMS
SteveSandersonMS merged commit ae7b7c2 into master Aug 30, 2018
@SteveSandersonMS
SteveSandersonMS deleted the stevesa/update-typescript-builds branch August 30, 2018 06:52
@ryanbrandenburg

Copy link
Copy Markdown
Contributor

@SteveSandersonMS, this PR targeted master, we need it in release/2.2 as well. I'm going to cherry-pick them back.

@SteveSandersonMS

Copy link
Copy Markdown
Member Author

Do you need it in 2.2 though? It’s just build infrastructure, not changing the resulting product.

@SteveSandersonMS

Copy link
Copy Markdown
Member Author

Well I guess there’s no reason not to cherry-pick to 2.2 as well. It will help if we need to make changes in 2.x patches.

ryanbrandenburg pushed a commit that referenced this pull request Aug 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants