`ust_parcel_bg.wasm' at '.my-app\crate\pkgresolve dependency './pkg`

[Aidiakapi]

Trying to initialize this template results in an error whilst running parcel.

D:\Projects\test>npm init rust-parcel my-app
npx: installed 1 in 1.85s
🦀Rust + 🕸 WebAssembly + Parcel = ❤️

D:\Projects\test>cd my-app

D:\Projects\test\my-app>npm install

> deasync@0.1.13 install D:\Projects\test\my-app\node_modules\deasync
> node ./build.js

`win32-x64-node-10` exists; testing
Binary is fine; exiting

> parcel-bundler@1.10.3 postinstall D:\Projects\test\my-app\node_modules\parcel-bundler
> node -e "console.log('\u001b[35m\u001b[1mLove Parcel? You can now donate to our open collective:\u001b[22m\u001b[39m\n > \u001b[34mhttps://opencollective.com/parcel/donate\u001b[0m')"

Love Parcel? You can now donate to our open collective:
 > https://opencollective.com/parcel/donate
npm WARN create-rust-parcel@0.0.1 license should be a valid SPDX license expression
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 734 packages from 544 contributors and audited 7644 packages in 10.773s
found 0 vulnerabilities


D:\Projects\test\my-app>npm run start

> create-rust-parcel@0.0.1 start D:\Projects\test\my-app
> parcel index.html

Server running at http://localhost:1234
ust_parcel_bg.wasm' at 'D:\Projects\test\my-app\crate\pkgresolve dependency './pkg
    at Resolver.resolve (D:\Projects\test\my-app\node_modules\parcel-bundler\src\Resolver.js:70:17)

Versions:
wasm-pack 0.5.1
cargo 1.32.0-nightly (1fa308820 2018-10-31)
rustc 1.32.0-nightly (25a42b2ce 2018-11-07)
parcel 1.10.3

OS: Windows 10
Steps to reproduce:

• npm init rust-parcel my-app
• cd my-app
• npm install
• npm run start

I ran the steps in cmd, Powershell and bash, but all of them resulted in the weird, kind of cut off error message. I've also ran the equivalent yarn instructions, but this doesn't change anything, so I can with some certainty say that the problem isn't with yarn or npm.

I'm not sure which of the dependencies is the source of the error, hence I'm filing the issue against this repo.

[sendilkumarn]

@Aidiakapi I think it may be due to some path issue in windows. I will try to find a win10 machine to test this out.