-
Notifications
You must be signed in to change notification settings - Fork 40
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
Convert build to webpack #200
Conversation
Codecov Report
@@ Coverage Diff @@
## master #200 +/- ##
=======================================
Coverage 39.39% 39.39%
=======================================
Files 84 84
Lines 2853 2853
Branches 531 531
=======================================
Hits 1124 1124
Misses 1610 1610
Partials 119 119
Continue to review full report at Codecov.
|
@triwav, @chrisdp, @georgejecook, Could you guys pull down this PR, build it, and make sure everything works well for you? It seemed to work just fine for me...but since completely changing the build system is a pretty substantial change, i'd feel better with a few other people validating that it works properly before I merge it. |
Seems to work for package, and I can build and run in vscode get these unit test failures.
|
What’s the status of this Pr? Is this moot due to our move to git workflows with v2? |
It's still something i'd like to do. It'll drastically reduce the the extension package size. However, I want to do more testing on it first to see if it's any slower during development. In my experience, the webpack projects I work on for my day job are usually a good bit slower, so before we make the switch I want to make sure it won't have a negative impact on our development cycle. It's not overly critical, so I'll get to it eventually. :D |
Closing in favor of #335 |
As per the recommendation of the vscode extension team, (that naggy message after every vsix build), I converted the build process to use webpack.