# Hanami Assets manifest in wrong place

**URL:** <https://discourse.hanakai.org/t/hanami-assets-manifest-in-wrong-place/927>\
**Category:** questions\
**Created:** [March 22, 2024, 8:48am UTC](https://discourse.hanakai.org/t/hanami-assets-manifest-in-wrong-place/927 "2024-03-22T08:48:06Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![timriley](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.hanakai.org/timriley/32/621_2.png) [@timriley](https://discourse.hanakai.org/u/timriley)\
**Post date:** [March 27, 2024, 12:58pm UTC](https://discourse.hanakai.org/t/hanami-assets-manifest-in-wrong-place/927/7 "2024-03-27T12:58:00Z")

</div>

@krzykamil OK, I think I’ve figured it out! There was something bogus in your package-lock.json, where the 2.1.0 version of hanami assets had a `"resolved"` URL [still pointing to a commit in the GitHub repo](https://github.com/krzykamil/libus/blob/03cb47fd1a008828b9ec488e64232900b0bd26a6/package-lock.json#L927-L929):

```json
"node_modules/hanami-assets": {
  "version": "2.1.0",
  "resolved": "git+ssh://git@github.com/hanami/assets-js.git#0627aa2a5fe2784f80d5590b070548085123f882",

```

This stood out to me because all the other packages in that file had `"resolved"` URLs pointing to the proper NPM registry, e.g.

```json
"resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.11.tgz",

```

Since hanami-assets 2.1.0 is a proper release in NPM, I wondered why it didn’t have a `registry.npmjs.org` URL like the one above.

To fix this in your app, I blew away `package-lock.json` as well as `node_modules`, and reinstalled fresh:

```auto
rm -rf package-lock.json node_modules
npm i

```

This resulted in the following section of diff for `package-lock.json`:

```diff
     "node_modules/hanami-assets": {
       "version": "2.1.0",
- "resolved": "git+ssh://git@github.com/hanami/assets-js.git#0627aa2a5fe2784f80d5590b070548085123f882",
- "license": "MIT",
+ "resolved": "https://registry.npmjs.org/hanami-assets/-/hanami-assets-2.1.0.tgz",
+ "integrity": "sha512-nOanYSZgATOrZofZXUwH7E1usTMbnECptaB6nfZCqNuE3QFCpRinOhdGJ8ndZPc1wEKVrs4VS85dQ0fLCa87Iw==",
       "dependencies": {
         "esbuild": "^0.19.0",
         "fs-extra": "^11.1.0",

```

That’s looking better!

Then a `bundle exec hanami assets compile` resulted in the following `public/assets/_main/assets.json`:

```json
{
  "app.js": {
    "url": "/assets/_main/app-FIQKTEJF.js"
  },
  "app.css": {
    "url": "/assets/_main/app-RRZUBCGY.css"
  },
  "favicon.ico": {
    "url": "/assets/_main/favicon-B8DAB077.ico"
  },
  "lib1.png": {
    "url": "/assets/_main/lib1-27767CE5.png"
  },
  "lib2.png": {
    "url": "/assets/_main/lib2-FBDB69C0.png"
  },
  "lib3.png": {
    "url": "/assets/_main/lib3-E9481CEB.png"
  },
  "seshat.png": {
    "url": "/assets/_main/seshat-F66A7922.png"
  },
  "NotoSans-Bold.ttf": {
    "url": "/assets/_main/NotoSans-Bold-F3484BDF.ttf"
  },
  "NotoSans-BoldItalic.ttf": {
    "url": "/assets/_main/NotoSans-BoldItalic-84A524F9.ttf"
  },
  "NotoSans-Italic.ttf": {
    "url": "/assets/_main/NotoSans-Italic-D5B99C1B.ttf"
  },
  "NotoSans-Regular.ttf": {
    "url": "/assets/_main/NotoSans-Regular-9A3CE638.ttf"
  }
}

```

Perfect!

So: there’s no bug in the 2.1.0 release of hanami-assets.

Somehow your app locked in a version in git that wasn’t doing the right thing. Interestingly, the `0627aa2a5fe2784f80d5590b070548085123f882` sha is actually [a commit](https://github.com/hanami/assets-js/commit/0627aa2a5fe2784f80d5590b070548085123f882) in this [currently open pull request](https://github.com/hanami/assets-js/pull/26), so I think we just need to be extra careful about testing that before merging and making a new release.

Let me know how you go in light of the information above!

---

_[View the full topic](https://discourse.hanakai.org/t/hanami-assets-manifest-in-wrong-place/927)._