Neutrinos Studio

Community Training, Academy & Certifications
1

Hi,

I was working on Neutrinos Studio using my personal system and encountered an issue while saving a task. The application suddenly crashed, and I was unable to reopen it. I had to reinstall the Studio to continue working.

I have a few questions regarding this incident:

  1. Branching Strategy:
    Does Neutrinos Studio support any branching strategy similar to Git or other version control systems? If so, could you guide me on how to use it effectively to manage and transfer tasks across systems?
  2. Task Transfer:
    Is there a recommended way to transfer or back up tasks from one system to another to avoid data loss in case of crashes?
  3. Crash Logs:
    When such crashes occur, are any logs stored locally that can help identify the root cause? If yes, please let me know where I can find them and how to share them for analysis.

I’d appreciate any guidance or documentation you can provide to help prevent such issues in the future and ensure smoother recovery.

@sumit.ghosh2 @Eldho

Thanks
Sagnik Chakraborty

2

@Sam @ragesh-a can you please help

3

:white_check_mark: 1 -:herb: Git Branching Strategy for Neutrinos Studio Projects

Neutrinos Studio does not provide a built-in branching strategy like Git. However, it integrates seamlessly with Git, and it’s highly recommended to manage your Neutrinos projects using version control systems such as Git for better collaboration, versioning, and backup.

:white_check_mark: Why Use Git with Neutrinos?

A Neutrinos project is structured like a standard Node.js application—meaning it consists of component files, services, routing configurations, etc. These files are fully compatible with Git workflows, allowing developers to:

  • Track changes
  • Roll back broken updates
  • Collaborate with teams
  • Review and merge code safely
  • Transfer or back up work across systems

:shuffle_tracks_button: Recommended Git Workflows

1. Feature Branch Workflow (Good for individuals or small teams)

  • Create a new branch for each task or feature.
  • Keeps the main or develop branch clean and production-ready.

Example:

git checkout -b feature/add-login
# Make your changes
git commit -am "Add login functionality"
git push origin feature/add-login

2. Gitflow Workflow (Ideal for structured teams)

  • A branching model with defined roles:
    • main: Stable, production-ready code
    • develop: Integration branch for features
    • feature/*, release/*, hotfix/*: Task-specific branches

Example:

git checkout -b feature/integrate-api develop
# Develop the feature
git checkout develop
git merge feature/integrate-api

:warning: Handling Merge Conflicts (Important!)

Merge conflicts can happen, especially when multiple developers are working on the same files (like components or layout files).

Scenario:

  • Developer A modifies home-layout.component.html
  • Developer B makes conflicting changes in another branch

Conflict markers example:

html

<<<<<<< HEAD
<div class="home-section">Welcome to our portal</div>
=======
<div class="home-section">Welcome to the updated dashboard</div>
>>>>>>> feature/update-dashboard

You’ll need to manually resolve the conflict and test the result.

Tips:

  • Communicate frequently with teammates
  • Pull from develop or main regularly
  • Resolve conflicts with caution to avoid losing work

:puzzle_piece: Git and Neutrinos File Structure

Neutrinos projects consist of real files and folders like:

  • src/app/components/
  • src/app/services/
  • config/

These can easily be committed, pushed, or cloned with Git. Just be sure to exclude environment-specific directories using a .gitignore file.

Suggested .gitignore:

node_modules/
.dist/
.angular/
logs/

:white_check_mark:2- :counterclockwise_arrows_button: Task Transfer & Backup Strategies for Neutrinos Studio

Here are two reliable methods to back up or transfer your projects safely across systems:

:white_check_mark: A. Git-Based Backup (Recommended)

Using Git is the most efficient and scalable way to manage your Neutrinos projects. It enables:

  • Seamless migration across systems
  • Protection against data loss
  • Collaboration across teams

Steps:

  1. Initialize a Git repo in your project folder:
git init
  1. Add your remote repository (GitHub, GitLab, Bitbucket, etc.):
git remote add origin <your-repo-url>
  1. Stage and commit your changes:
git add .
git commit -m "Initial commit"
  1. Push to your repository:
git push -u origin main
  1. On another system, simply clone the project:
git clone <your-repo-url>

:card_file_box: B. Manual Backup Using .nosbackup File

If you prefer manual methods or Git isn’t an option, you can use Neutrinos’ native backup feature:

Steps to Back Up:

  1. Export the .nosbackup file (if your Studio version supports it – this file contains project metadata and layout).
  2. Save the entire project folder, including:
  • .angular
  • .metadata
  • src/, components/, etc.
  1. Zip the folder and copy it to the destination machine.

Steps to Restore:

  1. Extract and open the folder in Neutrinos Studio on the new system.
  2. Install dependencies (if required):
npm install

:white_check_mark: 3. Crash Logs and Diagnostics

When Neutrinos Studio crashes, it stores helpful diagnostic logs locally.

:file_folder: Where to Find Logs:

  • Windows:
    C:\Users\<YourUsername>\.neutrinos\logs
  • macOS/Linux:
    ~/.neutrinos/logs

:magnifying_glass_tilted_left: Typical Files:

  • studio.log
  • error.log
  • electron-crash-report.log

These logs often include:

  • Stack traces
  • Missing dependency warnings
  • Electron-specific errors
  • Plugin/component failures
2 Likes