vankop
Repos
69
Followers
61
Following
26

react wrapper implementation for https://github.com/josdejong/jsoneditor

217
84

A mighty, modern linter that helps you avoid errors and enforce conventions in your styles.

9921
855

A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

61881
8127

Events

issue comment
`extensionAlias` is not applied to module exports

I fully agree with @alexander-akait idea => exports should work as written.

btw this seems wrong to me:

using exports field: ./index.js
              using description file: /home/remco/Projects/bug/node_modules/bar/package.json (relative path: ./index.js)
                no extension
                  Field 'browser' doesn't contain a valid alias configuration
                  /home/remco/Projects/bug/node_modules/bar/index.js doesn't exist
                .js
                  Field 'browser' doesn't contain a valid alias configuration
                  /home/remco/Projects/bug/node_modules/bar/index.js.js doesn't exist
                .ts
                  Field 'browser' doesn't contain a valid alias configuration
                  /home/remco/Projects/bug/node_modules/bar/index.js.ts doesn't exist
                as directory
                  /home/remco/Projects/bug/node_modules/bar/index.js doesn't exist

we should not apply extensions..

Created at 2 days ago
issue comment
webpack cache PackFileCacheStrategy

bump

Created at 2 days ago
started
Created at 2 days ago
Created at 4 days ago
Created at 1 week ago
Created at 3 weeks ago
closed issue
webpackMode: "weak" is fail, When module is in node_modules

Bug report

What is the current behavior? webpackMode: "weak" faile, when module is in node_modules

If the current behavior is a bug, please provide the steps to reproduce. https://stackblitz.com/edit/webpack-webpack-js-org-pdtara?file=src/component.jsx

What is the expected behavior? Load modules correctly

Other relevant information: webpack version: 5.38.1 Node.js version: v16.14.2

Created at 3 weeks ago
issue comment
webpackMode: "weak" is fail, When module is in node_modules

<C /> component is used so react-intl is used.. (Also it is used in index.jsx)

Created at 3 weeks ago
issue comment
Automatically tree shake dynamic imports without needing magic comments

it is hard to analyze all imports..

Created at 3 weeks ago
issue comment
strictExports: true is not enforced if unused module is empty

right now by default we have javascript/auto, this allows bundling esm+cjs together

Created at 3 weeks ago
closed issue
strictExports: true is not enforced if unused module is empty

Bug report

Similar to #4897

What is the current behavior?

Importing a non-existent named export from an empty module triggers no warning with strictExports: true

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

Repro: https://github.com/eps1lon/webpack-strict-exports-empty

What is the expected behavior?

export '...' was not found in '...'

Other relevant information: webpack version: 5.74.0 Node.js version: 16.14 Operating System: MacOS Monterey Additional tools:

Created at 3 weeks ago
issue comment
strictExports: true is not enforced if unused module is empty

@eps1lon set webpack.config

module.exports = {
  module: {
     rules: { type: "javascript/esm" }
  }
};

or in root package.json type: "module"

Created at 3 weeks ago
issue comment
require.context is not a function is ESM (type: module)

I think we should throw an error on empty import.meta.webpackContext()

Created at 3 weeks ago
opened issue
improve logger docs

Feature to document

see https://github.com/webpack/webpack/issues/12492#issuecomment-1210644980

Author(s)

Additional information

[ ] I am willing to work on this issue and submit a pull request.

Created at 3 weeks ago
opened issue
improve resolve error

Feature request

see https://github.com/webpack/enhanced-resolve/issues/354

What is the expected behavior?

more informative error message

What is motivation or use case for adding/changing the behavior?

How should this be implemented in your opinion?

Module not found error could be improved

Are you willing to work on this yourself? yes

Created at 3 weeks ago
Show more information when resolve exports field failed

image

Hope to show the module name

Created at 3 weeks ago
issue comment
Show more information when resolve exports field failed

This should be improved on webpack side, nothing todo in enhanced-resolve

Created at 3 weeks ago
issue comment
strictExports: true is not enforced if unused module is empty

sounds like with javascript/esm should be an error.. not sure.

Created at 3 weeks ago
issue comment
webpack native require doesn't work in windows

it looks like this code will not work on windows correctly

let filePath = resolve(__dirname, req.params[0])

request params has / instead of \

Created at 3 weeks ago
reopened issue
Webpack-native parallelism to obviate the need for the (unmaintained?) parallel-webpack package

Feature request

Per the webpack documentation , the package parallel-webpack is recommended to optimize multiple compilations. However, this package is increasingly outdated (it's not even specified for webpack 5). It would be good to have such functionality as a part of webpack itself, without relying on an outside project (that may itself be abandoned) to offer such support.

What is the expected behavior?

Webpack-native parallelism

What is motivation or use case for adding/changing the behavior?

The recommended package no longer appears to be actively maintained

How should this be implemented in your opinion?

I am not a lawyer, but the license of parallel-webpack suggests it might be possible to fork it directly.

Are you willing to work on this yourself?

not at this time

Related issue

https://github.com/trivago/parallel-webpack/issues/107

Created at 3 weeks ago
issue comment
Webpack-native parallelism to obviate the need for the (unmaintained?) parallel-webpack package

bump

Created at 3 weeks ago
issue comment
require.context is not a function is ESM (type: module)

bump

Created at 3 weeks ago
Terser is unable to minify `?` sign

Bug report

Actual Behavior

Minified code fails to run throwing a SyntaxError.

Expected Behavior

No syntax error should be thrown.

How Do We Reproduce?

We came across this in a function below

handleOutsideClick() {
    const { setModal } = this.props;
    const { activeModal } = this.state;

    const modals = { ...this.state.modals };

    if (modals[activeModal]?.opened) {
      setModal(null);
    }
 }

Question mark sign in if clause is the culprit of this issue. Replacing it with a normal undefined check seems to solve the issue.

Minifying it with the question mark sign results in: Browser: Uncaught SyntaxError: Unexpected token 'this' Minified code:

handleOutsideClick(){const{setModal:e}=this.props,{activeModal:t}=this.state;{...this.state.modals}[t]?.opened&&e(null)}

Please paste the results of npx webpack-cli info here, and mention other relevant information

  System:
    OS: macOS 12.5.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 76.42 MB / 16.00 GB
  Binaries:
    Node: 16.16.0 - /usr/local/bin/node
    npm: 8.11.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 105.0.5195.102
    Safari: 15.6.1
  Packages:
    css-loader: ^6.5.1 => 6.7.1 
    css-minimizer-webpack-plugin: ^3.3.1 => 3.4.1 
    file-loader: ^6.2.0 => 6.2.0 
    html-webpack-plugin: ^5.5.0 => 5.5.0 
    sass-loader: ^12.4.0 => 12.6.0 
    style-loader: ^3.3.1 => 3.3.1 
    terser-webpack-plugin: ^5.3.6 => 5.3.6 
    ts-loader: ^9.2.6 => 9.3.1 
    url-loader: ^4.1.1 => 4.1.1 
    webpack: ^5.65.0 => 5.74.0 
    webpack-bundle-analyzer: ^4.5.0 => 4.6.1 
    webpack-cli: ^4.9.1 => 4.10.0 
    webpack-dev-server: ^4.7.1 => 4.10.1 
    webpack-merge: ^5.8.0 => 5.8.0 
Created at 3 weeks ago
Terser is unable to minify `?` sign

please report to terser https://github.com/terser/terser

Created at 3 weeks ago
issue comment
Require.resolve not resolving for target:node bundles

you should get an error for require(f)() btw

Created at 1 month ago
issue comment
Paths to relative modules should be expressed as file names

this log

ERROR in ../node_modules/webpack/lib/FileSystemInfo.js 9:19-36
Module not found: Error: Can't resolve 'module' in '/home/work/s/REDACTED/node_modules/webpack/lib'
resolve 'module' in '/home/work/s/REDACTED/node_modules/webpack/lib'
  Parsed request is a module

looks like a webpack resolve error. Do you bundling webpack?

Created at 1 month ago
issue comment
Should contentHash happen before the moduleIds process?

if you have something like 1st webpack config with one moduleIds ( result in 1st content hash ) and change webpack config to another moduleIds => this will change content hash since module ids alaso a part of content..

Created at 1 month ago
issue comment
Should contentHash happen before the moduleIds process?

I saved my project in two version while their monaco-editor versions are identity.

what does it means? The important thing is when

import("monaco-editor") /* add a non-initial chunk */

happens with same configuration it should have same content hash (if editor was not changed)

Created at 1 month ago
issue comment
[webpack.cache.PackFileCacheStrategy] Restoring failed for ResolverCachePlugin. SyntaxError: Cannot use import statement outside a module

hm.. could you create small reproducible repo? I'll take a look

Created at 1 month ago
reopened issue
Preserve star exports for externalized dependencies in module output

Bug report

What is the current behavior? When code contains exports from externalized libraries, the export statements are not preserved in output when they should be.

If the current behavior is a bug, please provide the steps to reproduce. Simple isolated repro (with details in the README): https://github.com/dzearing/test-webpack-esm

We bundle a simple entry point which contains:

export * from '@fluentui/utilities';

We turn on output.library.type="module" in the webpack config and mark the library as external. The bundle preserved should still emit the export. Instead it contains a bunch of unexpected content:

import*as e from"@fluentui/utilities";var r={d:(e,t)=>{for(var o in t)r.o(t,o)&&!r.o(e,o)&&Object.defineProperty(e,o,{enumerable:!0,get:t[o]})},o:(e,r)=>Object.prototype.hasOwnProperty.call(e,r)};r.d({},{});

What is the expected behavior? The output should match the input and export * from the library.

webpack version: 5.67.0 Node.js version: 16.13.1 Operating System: Windows 11

Created at 1 month ago