Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to do releases upgrade ? #137

Closed
sondh0127 opened this issue Oct 16, 2020 · 3 comments
Closed

How to do releases upgrade ? #137

sondh0127 opened this issue Oct 16, 2020 · 3 comments
Labels
question Further information is requested

Comments

@sondh0127
Copy link

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?

@sondh0127 sondh0127 changed the title How to do releases update ? How to do releases upgrade ? Oct 16, 2020
@AhmedElywa
Copy link
Collaborator

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
image

@AhmedElywa AhmedElywa added the question Further information is requested label Oct 16, 2020
@sondh0127
Copy link
Author

sondh0127 commented Oct 16, 2020

@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:

  1. npm install -g @paljs/cli
  2. Go to the folder containing the old generated app
  3. 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

  1. git commit <old-app>
  2. npm install -g @paljs/cli
  3. generate new app with pal c <new-app>
  4. drop all new file from <new-app> to <old-app> folder => choose replace for all files
  5. revert unwanted changed

Screen Capture_select-area_20201016155451

Sometimes I think we also have to clean up node_modules yarn.lock.

> rm -rf .next node_modules yarn.lock
> yarn
  1. Generate with new cli
> pal g
> yarn generate
> yarn dev

Hope this helps!

@AhmedElywa
Copy link
Collaborator

AhmedElywa commented Oct 16, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants