Can't get project to run

[pgsandstrom]

I found this repo through vercel/next.js#13542

I had a similar problem in my own project (importing a shared folder from outside the project) but I couldn't get it to work. So I cloned this project, ran "yarn" and "yarn dev". But I just got an error very similar to the one I keep getting in my own project. Here is my full output from "yarn dev":

$ yarn dev
yarn run v1.22.4
$ yarn --cwd packages/web-app dev
$ next
ready - started server on http://localhost:3000
event - compiled successfully
event - build page: /
wait  - compiling...
error - ../bar/index.tsx 1:18
Module parse failed: Unexpected token (1:18)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> const Bar = () => <strong>bar</strong>
|
| export default Bar

My first thought is that I am on Windows, has the project been tested on that OS? I currently don' have acces to any other OS, so I cant confirm if that is the issue.

I'd be happy to contribute more details if you would find it helpful.

[pgsandstrom]

I just realized that your changes that would fix my problem actually wasn't merged with the PR. That explains why it didn't work, I should have read the thread more careful :) Anyway, I leave this issue open in case you want to do anything about it being in a broken state, but ofcourse I understand if you dont care.

[jeantil]

Hi, I'm on vacation at the moment so I won't look into it right away Some of the commits should be runnable but this is a demonstration and exploration repo so it is possible that the latest commits don't work as I may have started some further exploratory or left the repo in a State that only works with experimental builds of next make sure to check out the repo locally and look for commits that say "OK" ;) Even better I converted this repo into an integration test in the PR which demonstrates the same thing in a more stable way in next trunk, that would probably be a better place to look at :) Le mer. 19 août 2020 à 22:09, Per Sandstrom <[email protected]> a écrit :

…

I just realized that your changes that would fix my problem actually wasn't merged with the PR. That explains why it didn't work, I should have read the thread more careful :) Anyway, I leave this issue open in case you want to do anything about it being in a broken state, but ofcourse I understand if you dont care. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFTQ5XCMZVBTY4FCTCMI3SBQWN3ANCNFSM4QFJU4RA> .