Express - Unexpected token error after following instructions? about content HOT 6 OPEN

There's another one a bit further up, right below the "package.json" header", that's outdated.

Nope, that's the output generated by the application generator, as stated in the docs. What I am thinking of doing though is moving the instructions to patch this higher up so the text matches.

So the idea here is that they generate most of the code framework using the application generator. In the past the app gen was pretty close to current, so the slight difference in versions didn't matter. Now it does.

I wouldn't really recommend copy/pasting package.json. Running npm install everything you need sounds easier.

Probably not. The package file is generated by the application generator, and not all values are done with ^. So if you do update you only get a semantic update in the current minor.patch version.

In any case I actually want to fix the versions used so that I can choose when to update them. Why? Because that means this doesn't get broken whenever there is a big update - or at least the code runs for the listed dependencies.

Of course you're right as a general thing, but I've been maintaining this since I wrote it, and every time adding more flexibility to dependencies makes the cost of maintenance higher.

from content.

If you are using npm, what's your output of npm ls acorn?

from content.

[email protected] /Users/abbas/Documents/code/express/express-locallibrary-tutorial
└─┬ [email protected]
  ├─┬ [email protected]
  │ └─┬ [email protected]
  │   ├─┬ [email protected]
  │   │ └── [email protected] deduped
  │   └── [email protected]
  └─┬ [email protected]
    └─┬ [email protected]
      └── [email protected]

from content.

Thanks, @hamishwillee it looks the package versions specified in the tutorial are outdated—maybe it's time for a rewrite? :)

from content.

@Josh-Cena Yee of little faith. The dependencies were updated a week or so ago to match the very latest :-). I'd been trying not to do this because this uses the express application generator and I wanted to match that tools default output as much as possible to ease the job for developers.

@ajaffary Was probably unlucky enough to do the skeleton creation before then, which is why they look old. However that shouldn't be the cause of this problem since nothing else changed other than the dependencies, and they worked both before and after with no other changes.

@ajaffary The text that changed last week was in https://developer.mozilla.org/en-US/docs/Learn/Server-side/Express_Nodejs/skeleton_website#package.json - near the end:

Did you create the skeleton before last week? If not, that tells me I probably need to make this more visible.

In any case, can you rebuild with those dependencies and see what happens.

As I say though, I don't think that is the cause (though it may be). The worked project that was created by going through this tutorial is here: https://github.com/mdn/express-locallibrary-tutorial

It won't precisely match yours, but you should be able to compare and see if there are any obvious differences - and make sure your dependencies match?

from content.

There's another one a bit further up, right below the "package.json" header", that's outdated.

I wouldn't really recommend copy/pasting package.json. Running npm install everything you need sounds easier.

from content.