You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please confirm that you have searched existing issues in the repo
Yes, I have searched the existing issues
Any related issues?
No response
What is the area that this feature belongs to?
No response
Is your feature request related to a problem? Please describe.
It would be helpful to new developers to have instructions on how to migrate in the DG similiar to 'Migrating to Typescript'.
Describe the solution you'd like
Include checklist and steps needed for migrating in DG.
This can take reference from what was done in #2233 when migrating to node v16 from v14
Left with one TODO:
After Specify Netlify build settings #2277, the netlify setting for deploying our documentation on markbind-master is configured using the netlify.toml in our root folder. When migrating, we should change the Node.js version specified in that file accordingly. Hence, we should mention this step in the migrating to Node.js docs
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
@jovyntls I think so, but I realized I accidentally introduced a place that needs updating the docs for (#2277). Will modify and make use of this issue for that.
tlylt
changed the title
Add documentation on migrating Node.js
Add note on netlify config when migrating Node.js
Apr 15, 2023
Please confirm that you have searched existing issues in the repo
Yes, I have searched the existing issues
Any related issues?
No response
What is the area that this feature belongs to?
No response
Is your feature request related to a problem? Please describe.
It would be helpful to new developers to have instructions on how to migrate in the DG similiar to 'Migrating to Typescript'.
Describe the solution you'd like
Include checklist and steps needed for migrating in DG.
This can take reference from what was done in #2233 when migrating to node v16 from v14
Left with one TODO:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: