Closed sondh0127 closed 3 years ago
Hi @sondh0127, you always can look to releases notes here and see if there any breaking changes, or you can just update without any change in your code
Also, you can watch release notes. to get an email when any new release released
@AhmedElywa Thank you for your answer but this isn't what I mean. I would like to do that with paljs/cli instead. Something like:
pal c <the_old_foldername>
After that, I'll be able to see the diff of each file.
I ended up with the following step with the help of Vscode + Git
<old-app>
npm install -g @paljs/cli
pal c <new-app>
<new-app>
to <old-app>
folder => choose replace for all files
Sometimes I think we also have to clean up
node_modules
yarn.lock
.rm -rf .next node_modules yarn.lock yarn
- Generate with new cli
pal g yarn generate yarn dev
Hope this helps!
we don't make many changes in the examples files, but if you need to know what we change in these examples, there is an easier way to do this look to the new commit into this folder and see what we change. and by clicking on History you will see the last commits in this folder
Did we have any approach to upgrade the current project?
I create a project with "@paljs/generator": "^2.3.1". so how can I update to ^2.3.2 automatically or provide some way to resolve the conflict?