Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The plugin is not compatible with Windows

See original GitHub issue

I am assuming the port is in use:

{ Error: listen EACCES C:\Users\...\Temp\tmp-90492gfaNZ4bpHiqO
    at Object._errnoException (util.js:1022:11)
    at _exceptionWithHostPort (util.js:1044:20)
    at Server.setupListenHandle [as _listen2] (net.js:1334:19)
    at listenInCluster (net.js:1392:12)
    at Server.listen (net.js:1487:5)
    at Function.listen (D:\...\node_modules\express\lib\application.js:618:24)
    at new Server (D:\...\node_modules\parcel-plugin-typescript\build\ipc\server.js:27:14)
    at new TypeScriptServer (D:\...\node_modules\parcel-plugin-typescript\build\backend\worker\index.js:28:9)
    at module.exports (D:\...\node_modules\parcel-plugin-typescript\build\index.js:16:24)
    at Bundler.loadPlugins (D:\...\node_modules\parcel-bundler\src\Bundler.js:102:17)
    at <anonymous>
  code: 'EACCES',
  errno: 'EACCES',
  syscall: 'listen',
  address: 'C:\\Users\\...\\Temp\\tmp-90492gfaNZ4bpHiqO',

The plugin errors but the build continues, resulting in paths not being rewritten.

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

SleeplessBytecommented, Jan 18, 2018

Thanks man! This has been working for me since 9722f10!

1reaction

fathybcommented, Jan 11, 2018

I published parcel-plugin-typescript@0.4.2-next.2 to support entirely Windows. If you confirm me it works for you I’ll publish it as 0.5.0. (you can remove the transpileOnly workaround)