# Upgrading an older Project, to have Prototyper

**URL:** https://community.firebasestudio.dev/t/upgrading-an-older-project-to-have-prototyper/12986
**Category:** Project Templates
**Created:** [May 22, 2025, 5:42pm UTC](https://community.firebasestudio.dev/t/upgrading-an-older-project-to-have-prototyper/12986 "2025-05-22T17:42:11Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![DaC](https://sea2.discourse-cdn.com/flex002/user_avatar/community.firebasestudio.dev/dac/32/6866_2.png) [@DaC](https://community.firebasestudio.dev/u/DaC)
#### Post date: [May 22, 2025, 11:38pm UTC](https://community.firebasestudio.dev/t/upgrading-an-older-project-to-have-prototyper/12986/2 "2025-05-22T23:38:28Z")

</div>

- Start a new project, prototype anything, just ask for something very very simple.
- when it’s done, go to the backend \<\>
- delete files created (keep idx, and gitignore), upload your project files (skip any cache, node modules or anything else that is build on start)
- run the command: npm install
- when it’s done, go firevase studio homescreen and reset the project
- load the project and you prompt the prototyper normally
- tell him you made an extensive change in the code base and that he must read the entire codebase to get to know the project.
- then tell him for now on to disregard any code he created while prototyping, including the project idea/blueprint and to stick to the current project he just red.

This should work, if it doesn’t try to reset again, still not working, start debugging with the prototyper sending him the terminal errors from the development interface.

you can reference this post for more details on the procedure, although this was for projects already created, it works with your case too just with less steps:

> [@Prototyper history gone, now what?](https://community.firebasestudio.dev/t/prototyper-history-gone-now-what/12354/13):
>
> \*\* A few hours later \*\*… yepz, got to do a reset again and he forgot everything this time and wants to prototype the app again, no matter I say he won’t look into the code base… any workround ? I think the main problem is this, the prototyper should be able to realize there’s a project already and go trough it to get the necessary context instead of trying to start over \*\* A few minutes later \*\* I GOT THE WORKAROUND FOLKS! here is what I did: although the old prototyper memory was gone, the p…

---

_[View the full topic](https://community.firebasestudio.dev/t/upgrading-an-older-project-to-have-prototyper/12986)._