Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Source maps for scss files produced by webpack contains duplicate parts like C:\...C:\...\some-file.scss.

I'd like to use relative paths but I can't understand why webpack use absolute paths for css files.

If the current behavior is a bug, please provide the steps to reproduce.

There is my loaders configuration for scss files:

loader: [
"style-loader",
{
loader: "css-loader",
options: {
sourceMap: true,
minimize: true,
importLoaders: 2
}
},
{
loader: "postcss-loader",
options: {
sourceMap: true,
plugins: function () {
return [
require("autoprefixer")({
browsers: ["last 4 versions"]
})
];
}
}
},
{
loader: "sass-loader",
options: {
sourceMap: true
}
},
"sass-bulk-import-loader"
]

What is the expected behavior?

The source map file have to containe one absolute or relative path to the source file.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

webpack 2.2,1 but I also tested with 2.6.1 and the problem is the same

node.js 7.7.4

"style-loader": "^0.13.1"

"css-loader": "^0.28.4",

"postcss-loader": "^2.0.5",

"autoprefixer": "^7.1.1",

"node-sass": "^4.5.2",

"sass-loader": "^6.0.5"

Windows 7

Issue 2:
Bug report

Cannot build a webpack project with the latest SDK installed, @aws-sdk/lib-storage@3.17.0. I get the following error: Module not found: Error: Can't resolve 'fs' in ...

Setup

Below is the minimal setup for reproducing this problem.

$ tree
.
├── package-lock.json
├── package.json
└── src
└── index.js

1 directory, 3 files

Contents of package.json:

{
"name": "ttt",
"version": "1.0.0",
"private": true,
"scripts": {
"build": "webpack --mode development"
},
"devDependencies": {
"webpack": "^4.46.0",
"webpack-cli": "^3.3.12",
"webpack-dev-server": "^3.11.2"
},
"dependencies": {
"@aws-sdk/client-s3": "^3.17.0",
"@aws-sdk/lib-storage": "^3.17.0"
}
}

Contents of src/index.js:

import { S3Client } from '@aws-sdk/client-s3';
import { Upload } from '@aws-sdk/lib-storage';

console.log('+=+ S3Client', S3Client);
console.log('+=+ Upload', Upload);

What is the current behavior?

I get the following error:

ERROR in ./node_modules/@aws-sdk/lib-storage/dist/es/runtimeConfig.js
Module not found: Error: Can't resolve 'fs' in '/Users/korya/dev/ttt/node_modules/@aws-sdk/lib-storage/dist/es'
@ ./node_modules/@aws-sdk/lib-storage/dist/es/runtimeConfig.js 3:0-31 7:106-115
@ ./node_modules/@aws-sdk/lib-storage/dist/es/bytelength.js
@ ./node_modules/@aws-sdk/lib-storage/dist/es/Upload.js
@ ./node_modules/@aws-sdk/lib-storage/dist/es/index.js
@ ./src/index.js

If the current behavior is a bug, please provide the steps to reproduce.

Create the project

Install deps: npm install

Try to build it using npm run build (or just by running npx webpack)

What is the expected behavior?

The project should be successfully built and Upload imported @aws-sdk/lib-storage should be configured to work in browser's environment (as expected).

Other relevant information:

webpack version: 4.46.0

Node.js version: 15.14.0

npm version: 7.12.1

Operating System: MacOS Catalina

Additional tools: