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
Vite 3 ãŒæŽ¡ç”¨ã—㟠CJS Proxy ã«ã‚ˆã‚‹ Dual Package 構æˆ
2022 å¹´ç¾åœ¨ã€Node.js 界隈㯠ESM (ES Module) ã¸ã®ç§»è¡Œã®éŽæ¸¡æœŸã§ã‚ã‚Šã€ç‰¹ã«æ—¢å˜ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã«ãŠã„ã¦ã¯ CJS (CommonJS) 構æˆã§ã‚ã‚‹ã“ã¨ãŒã¾ã ã¾ã 多ã„。ã¾ãŸã€Pure ESM 㪠npm パッケージã¯ã€CSJ プãƒã‚¸ã‚§ã‚¯ãƒˆã‹ã‚‰ã®åˆ©ä¾¿æ€§ãŒæ‚ªãã€dynamic import ãŒå¿…é ˆã§éžåŒæœŸåŒ–ã‚’å¼·ã„られãŸã‚Š TypeScript ã®è¨å®šå¤‰æ›´ãŒå¿…è¦ã ã£ãŸã‚Šã¨é¢å€’ãŒå¢—ãˆã‚‹ã€‚ ãã‚“ãªçŠ¶æ³ã®ãŸã‚ã€åºƒã使ã‚ã‚ŒãŸã„ npm パッケージを公開ã™ã‚‹å ´åˆã€importã§ã‚‚requireã§ã‚‚利用ã§ãるよㆠdual package 構æˆã‚’å–ã‚ŠãŸããªã‚‹ãŒã€å®šç•ªæ‰‹æ³•ãŒç¢ºç«‹ã—ã¦ã„ã‚‹ã¨ã¯è¨€ãˆãšã€æ„外ã¨é¢å€’ãŒå¤šã„。よã見るã®ã¯ã€tscã‚„esbuildç‰ã§ ESM 用㨠CJS 用ã®è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚’用æ„ã—ã¦ãã‚Œãžã‚Œåˆ¥ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã«å‡ºåŠ›ã—ã€ãƒ‘ッケージã«ä¸¡æ–¹åŒæ¢±ã—㦠conditional ex
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
feat!: migrate to ESM by antfu · Pull Request #8178 · vitejs/vite
feat: importing ts files using their corresponding js extesions by haoqunjiang · Pull Request #5510 · vitejs/vite
{{#tags}}- {{label}}
{{/tags}}