# Need to restart Ember in order to test front-end changes
**URL:** https://meta.discourse.org/t/need-to-restart-ember-in-order-to-test-front-end-changes/246069
**Category:** Development
**Created:** [November 18, 2022, 5:03pm UTC](https://meta.discourse.org/t/need-to-restart-ember-in-order-to-test-front-end-changes/246069 "2022-11-18T17:03:45Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@SilK](https://meta.discourse.org/u/SilK)
#### Post date: [November 18, 2022, 5:03pm UTC](https://meta.discourse.org/t/need-to-restart-ember-in-order-to-test-front-end-changes/246069/1 "2022-11-18T17:03:46Z")
Hey there!
I’ve set up a new dev environment for working on plugins. Discourse is up to date with the main branch.
I need to restart Ember in order to test changes made to the front end. This includes changes to Handlebars, Emberjs, and stylesheets. A few months ago, when I was working on plugins, I only needed to reload the web page to test these changes.
Has something changed in this time? Is this something wrong with my environment?
Any help is much appreciated! 🙂
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [November 18, 2022, 5:19pm UTC](https://meta.discourse.org/t/need-to-restart-ember-in-order-to-test-front-end-changes/246069/2 "2022-11-18T17:19:24Z")
Changes to frontend code should only require a refresh of the page. In fact, a change to JS code should actually trigger a browser refresh automatically.
So it sounds like something is wrong with your environment. Did you follow one of the development installation guides here on Meta?
---
### Author:  [@SilK](https://meta.discourse.org/u/SilK)
#### Post date: [November 18, 2022, 5:20pm UTC](https://meta.discourse.org/t/need-to-restart-ember-in-order-to-test-front-end-changes/246069/3 "2022-11-18T17:20:47Z")
That’s along the lines of what I figured it should occur.
This is the installation guide I followed. I should mention I am using an Ubuntu subsystem with Windows 11 WSL.
> [@Install Discourse on Ubuntu or Debian for Development](https://meta.discourse.org/t/install-discourse-on-ubuntu-for-development/14727):
>
> warning This guide covers installation instructions in a development environment. For a production guide see: [Install Discourse in production with the official supported instructions](https://meta.discourse.org/t/how-to-install-discourse-in-production/142537) So you want to set up Discourse on Ubuntu or Debian to hack on and develop with? We’ll assume that you work locally and don’t have Ruby/Rails/Postgres/Redis installed on your Ubuntu or Debian system. Let’s begin! Requirements We suggest having at least 4 GB RAM and 2 CPU cores. Current compatibility: O…
---
### Author:  [@SilK](https://meta.discourse.org/u/SilK)
#### Post date: [November 18, 2022, 6:17pm UTC](https://meta.discourse.org/t/need-to-restart-ember-in-order-to-test-front-end-changes/246069/4 "2022-11-18T18:17:53Z")
Ended up finding the issue: My environment had some symbolic links that (I assume) were messing up file change detections.
The discourse and my-plugin directories were under my Windows user, with symbolic links in the WSL Ubuntu (/home/silk/discourse → /mnt/c/Users/SilK/discourse).
The resolution was to have the true directories exist in the WSL Ubuntu environment, and create Windows symbolic links (C:\Users\SilK\discourse → \wsl.localhost\Ubuntu-20.04\home\silk\discourse).
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [December 18, 2022, 6:18pm UTC](https://meta.discourse.org/t/need-to-restart-ember-in-order-to-test-front-end-changes/246069/5 "2022-12-18T18:18:26Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.