What is the approach are you using to serve the website in production?

[nazarepiedady]

I am working on a localised version of this website that serves the documentation in Portuguese. I did recently update the source code to match the updates and changes done in this repository. Still, I am struggling to serve the new codebase because it is breaking everything at all times, I am really without brilliant ideas about the solution to the problem.

I am serving the website through Netlify services since it was using the middleman static site generator, and this is the traceback of the errors I am having. Could you say what I am doing wrong below?

I am saving the source code here: https://github.com/nazarepiedady/sass-docs-pt

[nazarepiedady]

@nex3 could you provide some light to the problem?

[nex3]

It looks like your Netlify instance already has a .language directory checked out, and that this directory has a modified package-lock.json file which is causing git to fail when it attempts to check out the latest revision. I'm not sure why that directory would exist already or persist across deploys, though. Is it possible that you have some caching setting turned on?

[nazarepiedady]

Yes @nex3 , the caching feature of the Netlify platform is enabled, because this allows me not to serve a broken website when a new build fail.

So what is your suggestion or what do you recommed to solve this problem?

Do you think that if I delete the package-lock.json file this problem will be solved?

[nex3]

I think you need to disable caching, so that this runs a clean build from scratch each time.

[nazarepiedady]

@nex3 thanks, you saved me.

I am closing this issue because the problem is already solved.