susiwen8

I think this is correct behaviour, cause esbuild will bundle all file into single file, the structure looks like ``` -dist -test.js -node_modules -src -test.ts -a -a.ts -b -b.ts ```...

> it feels like the expected behaviour should be the import path is relative to `outbase` for each file I second that

Sorry I don't have use case. the reason that I raised this issue just want to optimize bundle size. Well I have to admit, this might be over optimize. Say...

Hi @evanw , what do you think about this?

https://github.com/evanw/esbuild/commit/ac97be74c3b5453740f84fc40098ccae95cde19f You can see the reason in change log

Oh, sorry, I see

I think it's better not throwing error under `watch` mode at first build.

> For a given import path, all `onResolve` callbacks from all plugins will be run in the order they were registered until one takes responsibility for path resolution. Looks like...

function test(str) { str = str.split('').map(item => { if (item === item.toUpperCase()) { return item.toLowerCase(); } else { return item.toUpperCase(); } }).join(''); console.log(str); }

function test(len, range) { let test = []; for (let i = 0; i < len; i++) { test.push(Math.round(Math.random() * range)); } test = Array.from(new Set(test)).sort((a, b) => a -...