-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected token HashRouter. #163
Comments
Hmm, I just tried a fresh clone and didn't run into this. Perhaps an issue with npm's cache? If clearing that doesn't help can you provide more info like your OS, |
Verifying the cache as npm suggests.
Here are the versions while I try forcing a clean of the cache.
|
After |
Very strange.. 🤔 |
[:~/dev/lumi/purescript-lumi-components] main 31s 130 ±
> npx pulp --version
Pulp version 13.0.0
purs version 0.13.6 using /Users/maddie/dev/lumi/purescript-lumi-components/node_modules/.bin/purs
[:~/dev/lumi/purescript-lumi-components] main ±
> npm ls webpack
[email protected] /Users/maddie/dev/lumi/purescript-lumi-components
└── [email protected]
[:~/dev/lumi/purescript-lumi-components] main 2s ±
> npm --version
6.14.5
[:~/dev/lumi/purescript-lumi-components] main ±
> node --version
v14.3.0 |
@philderbeast Can you try commenting out this line? |
It works for me now with that one line taken out. Thanks @spicydonuts. |
I did a fresh clone and this time didn't encounter the error. I see the line I commented out last time for the build has not changed but I have now installed bower, pulp, purescript and spago globally. I did this to try other projects without such hermetic builds as this one. |
Odd. I was using the npx commands so we should have been on the same local versions. I don't get why excluding unrelated folders affects whether |
I followed the steps for local development from the readme and saw the following error.
The text was updated successfully, but these errors were encountered: