Add polyfill for path to fix a bug that prevented the results view from being loaded#842
Merged
alexet merged 2 commits intogithub:mainfrom Apr 23, 2021
henrymercer:henrymercer/add-path-polyfill
Merged
Add polyfill for path to fix a bug that prevented the results view from being loaded#842alexet merged 2 commits intogithub:mainfrom henrymercer:henrymercer/add-path-polyfill
alexet merged 2 commits intogithub:mainfrom
henrymercer:henrymercer/add-path-polyfill
Conversation
Webpack >v5 doesn't include polyfills for core modules from Node.js by default. Since we use `path` in the results table UI, we need to include our own polyfill. This commit adds `path-browserify` to the distributed extension. As future work, we could move SARIF location rendering into the core extension so we don't need to use `path.basename` in the UI. This would allow us to remove the polyfill.
alexet
approved these changes
Apr 23, 2021
aofaof0907
pushed a commit
to aofaof0907/vscode-codeql
that referenced
this pull request
Jul 27, 2021
…om being loaded (github#842) * Add a polyfill for the Node.js path module Webpack >v5 doesn't include polyfills for core modules from Node.js by default. Since we use `path` in the results table UI, we need to include our own polyfill. This commit adds `path-browserify` to the distributed extension. As future work, we could move SARIF location rendering into the core extension so we don't need to use `path.basename` in the UI. This would allow us to remove the polyfill. * Add changelog note
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Webpack >=v5 doesn't include polyfills for core modules from Node.js by default. Since we use
pathin the results table UI, we need to include our own polyfill. This PR addspath-browserifyto the distributed extension.As future work, we could move SARIF location rendering into the core extension so we don't need to use
path.basenamein the UI. This would allow us to remove the polyfill.Checklist
@github/docs-content-codeqlhas been cc'd in all issues for UI or other user-facing changes made by this pull request.