A Proposal For Module Resolution · Issue #50152 · microsoft/TypeScript
Background When a user writes a module specifier (the string literal after from in an import declaration) in a TypeScript file, how should the compiler resolve that string to a file on disk to be included in type checking? Because TypeScript never rewrites module specifiers in its JavaScript emit, the only possible answer is that it should mirror whatever resolution behavior the code’s intended ru
Chrome extension compiled by Webpack throws `unsafe-eval` error
I get this error when reloading my Chrome Extension after compiling using Webpack: Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' blob: filesystem: chrome-extension-resource:". at new Function (<anonymous>) at evalExpression (compiler.js:33919) at jitState
Roadmap 2021 (2020-12-08) | webpack
It has been nearly 2 months since webpack 5 was officially released. Due to the sponsoring situation, we couldn't devote as much time to webpack as we would like to. Speaking only for myself (@sokra), I enjoyed the little break and have worked on a few side projects. Ironically, while I was using webpack 5 and all its bleeding-edge features (asset modules, worker support, persistent caching), I di
ESM-CJS interop test
ESM-CJS interop test Test Cases Results Node.js Babel Webpack Rollup.js Parcel esbuild Results by test case Results by syntax import x and similar import { named } and similar import { __esModule } and similar import * and similar import() and similar require().default and similar require().named and similar require().__esModule and similar require() and similar Direct differences Webpack <-> Node
Webpack 5 Headache
Webpack no longer automatically polyfills Node.js APIs. This is a huge breaking change and will inconvenience both users and package maintainers. Most packages on npm are mainly made with Node.js in mind. However, thanks to automatic polyfilling, most of them have for years worked fine in the browser too. The problem is that Webpack created convenience by automatically polyfilling and then now sud
importæ–‡ã§ç”»åƒã‚„CSSã‚’èªã¿è¾¼ã‚€ã®ã¯ECMAScript仕様é•åã‹ - uhyo/blog
è¿‘é ƒã®JavaScript開発ã¯ã€ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã¨ã—ã¦æ›¸ã‹ã‚ŒãŸè¤‡æ•°ã®JavaScriptファイルをimport文やexport文を通ã˜ã¦é€£æºã•ã›ã‚‹ã®ãŒåŸºæœ¬ã§ã™ã€‚ã¾ãŸã€ãれらã®ãƒ•ã‚¡ã‚¤ãƒ«ã¯Webpackã«ä»£è¡¨ã•ã‚Œã‚‹ãƒãƒ³ãƒ‰ãƒ©ã«ã‚ˆã£ã¦äº‹å‰ã«å‡¦ç†ã•ã‚Œã€importæ–‡ã®è§£æ±ºãƒ»ãƒ•ã‚¡ã‚¤ãƒ«ã®çµåˆã¨ã„ã£ãŸå‰å‡¦ç†ã‚’æ–½ã•ã‚Œã‚‹ã®ãŒæ™®é€šã§ã™ã€‚ã¾ã£ãŸãã€å„ファイルãŒä»–ã«å½±éŸ¿ã‚’与ãˆãªã„よã†ã«(function(){ ... })()ã§å›²ã‚“ã§æ–‡å—列連çµã—ã¦ã„ãŸæ™‚代ãŒæ‡ã‹ã—ã„ã§ã™ã。 ã•ã¦ã€importæ–‡ã®è§£æ±ºã‚’担当ã™ã‚‹ãƒãƒ³ãƒ‰ãƒ©ã¯ã€å¤§æŠµJavaScriptプãƒã‚°ãƒ©ãƒ 以外ã®ã‚‚ã®ã‚’èªã¿è¾¼ã‚€æ©Ÿèƒ½ã‚’å‚™ãˆã¦ã„ã¾ã™ã€‚Webpackãªã‚‰ã°loaderã¨å‘¼ã°ã‚Œã‚‹ã‚‚ã®ã§ã™ã。例ãˆã°ã€style-loaderã‚„css-loaderãŒæŒã¤CSS Modulesã®æ©Ÿèƒ½ã‚’使ã†ã¨æ¬¡ã®ã‚ˆã†ãªãƒ—ãƒã‚°ãƒ©ãƒ を書ãã“ã¨ãŒã§ãã¾ã™ï¼ˆReactã®ä¾‹ï¼‰ã€‚ import s
webpackã®æ¬¡ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§å…¥ã‚‹assetModulesã®ç´¹ä»‹ - 技術探ã—
ã“ã®æ©Ÿèƒ½ãŒå°Žå…¥ã•ã‚Œã‚‹ã“ã¨ã«ã‚ˆã‚Šã€{raw/file/url}-loader ãŒä¸è¦ã¨ãªã‚Šã¾ã™ã€‚ webpack@4 ã§ã‚‚使ãˆã¾ã™ãŒã€ã¾ã 実験的フェーズã§ã™ã€‚ Documentation Asset Modules | webpack webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.
ランã‚ング
ランã‚ング
メンテナンス
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
https://twitter.com/youyuxi/status/1585040261922820096
GitHub - FredKSchott/esm-hmr: a Hot Module Replacement (HMR) API for your ESM-based dev server.
add extension alias by vankop · Pull Request #351 · webpack/enhanced-resolve
GitHub - webpack/enhanced-resolve: Offers an async require.resolve function. It's highly configurable.
GitHub - codepunkt/webpack-license-plugin: Manage third-party license compliance in your webpack build
Release v5.66.0 · webpack/webpack
Breaking change with import via CommonJS in `2.5.0` · Issue #896 · webpack-contrib/mini-css-extract-plugin
GitHub - niksy/node-stdlib-browser: Node standard library for browser.
GitHub - TypeStrong/fork-ts-checker-webpack-plugin: Webpack plugin that runs typescript type checker on a separate process.
GitHub - merkle-open/webpack-config-plugins: Provide best practices for webpack 4 loader configurations
GitHub - google/strict-csp
slides/content/ModuleFederationWebpack5.md at master · sokra/slides
{{#tags}}- {{label}}
{{/tags}}