Javi Martín
Javi Martín
One more thing to try: in the `app/assets/stylesheets/foundation_and_overrides.scss` file, comment (don't delete, so line numbers remain the same) lines 10, 49 and 50 (which are the lines referencing `motion-ui`. Then...
> the entire sub-fofder node_modules/motion-ui/ does not exist. OK, this seems to be the issue. In my case, it happens sometimes when running `npm install` on a branch and then...
> It is not referenced. Which branch are you using? :thinking: The `master` branch? The `2.1.1` tag? Any other?
OK, so, after restoring the original `package-lock.json`, remove `public/assets` if it exists, run `npm install` and start the application. It should work :crossed_fingers:.
> [email protected] I'm confused :thinking:. The `package-lock.json` file in the `master` branch contains: ``` "node_modules/foundation-sites": { "version": "6.7.5", ``` So I'm not sure why version 6.8.1is mentioned in the warnings....
Which versions of Node.js and NPM are you using, by the way?
Not sure if this is what's causing the issue :thinking:, but the application requirements mention Node.js 18.18.2.
Looks like it, yes.
Unfortunately we haven't updated the documentation regarding how to install Node.js on development yet (EDITED As of August 2024, the documentation is now updated; see pull request #5652). Personally, I...
So, if I understand it correctly, after running `npm install`, you don't have a `node_modules` folder?