diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml deleted file mode 100644 index 5e7c7b6d..00000000 --- a/.github/FUNDING.yml +++ /dev/null @@ -1 +0,0 @@ -open_collective: webpack diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index d6149050..00000000 --- a/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,36 +0,0 @@ -#### Issue description -... - -#### Technical info - - - -
-REPLACE THIS TEXT WITH THE OUTPUT FROM THE COMMAND ABOVE -- -#### Debug info -How do you use this module? As CLI utility or as plugin? - -If CLI, what command was used? (e.g. `webpack-bundle-analyzer -O path/to/stats.json`) - -If plugin, what options were provided? (e.g. `new BundleAnalyzerPlugin({ analyzerMode: 'disabled', generateStatsFile: true })`) - -What other Webpack plugins were used? - -It would be nice to also attach webpack stats file. -It can be generated using these options: -```js -new BundleAnalyzerPlugin({ - analyzerMode: 'disabled', - generateStatsFile: true, - // Excludes module sources from stats file so there won't be any sensitive data - statsOptions: { source: false } -}) -``` -`stats.json` will be created in Webpack bundle output directory. diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 29f51de4..5a73989a 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -2,7 +2,7 @@ name: main on: push: branches: - - master + - main pull_request: jobs: build-and-test: diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d2566da7..89a213b9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -48,11 +48,11 @@ If your own project's Webpack config has `BundleAnalyzerPlugin` configured with We'd love for you to contribute your changes back to `webpack-bundle-analyzer`! To do that, it would be ace if you could commit your changes to a separate feature branch and open a Pull Request for those changes. -Point your feature branch to use the `master` branch as the base of this PR. The exact commands used depends on how you've setup your local git copy, but the flow could look like this: +Point your feature branch to use the `main` branch as the base of this PR. The exact commands used depends on how you've setup your local git copy, but the flow could look like this: ```sh # Inside your own copy of `webpack-bundle-analyzer` package... -git checkout --branch feature-branch-name-here upstream/master +git checkout --branch feature-branch-name-here upstream/main # Then hack away, and commit your changes: git add -A git commit -m "Few words about the changes I did" diff --git a/README.md b/README.md index 56c1e6ca..99b8a156 100644 --- a/README.md +++ b/README.md @@ -81,7 +81,7 @@ command: webpack --profile --json > stats.json ``` -If you're on Windows and using PowerShell, you can generate the stats file with this command to [avoid BOM issues](https://github.com/webpack-contrib/webpack-bundle-analyzer/issues/47): +If you're on Windows and using PowerShell, you can generate the stats file with this command to [avoid BOM issues](https://github.com/webpack/webpack-bundle-analyzer/issues/47): ``` webpack --profile --json | Out-file 'stats.json' -Encoding OEM @@ -183,7 +183,7 @@ It happens when `webpack-bundle-analyzer` analyzes files that don't actually exi Error parsing bundle asset "your_bundle_name.bundle.js": no such file No bundles were parsed. Analyzer will show only original module sizes from stats file. ``` -To get more information about it you can read [issue #147](https://github.com/webpack-contrib/webpack-bundle-analyzer/issues/147). +To get more information about it you can read [issue #147](https://github.com/webpack/webpack-bundle-analyzer/issues/147).