Upgrading from 1.7.3 to 2.X was unsuccessful

Open
#3,515 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
24/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vite, vscode

Research direction

Start by reading the migration guide for the 1.7.3 to 2.X upgrade and the VS Code launch.json setup described in the report. Reproduce the workflow with Vite and check whether breakpoints work in source files; also determine whether development without Vite is supported. Done means the debugging setup and workflow guidance are clear, but the issue does not identify specific files or tests.

Written by the indexing model from the issue text.

Description

bug upstream

My experience upgrading from 1.7.3 to 2.X was unsuccessful. I followed the migration guide to upgrade my project to 2.X. The biggest problem was that VS Code could not properly configure launch.json. Even if the configuration seemed successful and the project started, I could not set breakpoints in the source code, which is unacceptable. Therefore, I rolled back. I hope there will be best practices and better documentation guidance.

I want to know if 2.X projects are still considered immature at this point.

For context, I am using Vite. I would like to know whether 2.X supports development workflows that do not use Vite.

Dominant language
TypeScript
Stars
13.8k
Forks
757
Avg merge
3m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from freshframework/fresh

All issues in freshframework/fresh

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.