{{ROOT_URL}} (for registration) not getting replaced during build
See original GitHub issueall I have is this (in my ember-cli-config):
'ember-service-worker': { },
but in the output, I’m getting:
(function(){"use strict"
function n(n){e.push(n)}var e=[],r=[]
"serviceWorker"in navigator&&navigator.serviceWorker.register("{{ROOT_URL}}sw.js",{scope:"{{ROOT_URL}}"}).
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Can we change root APIURL in angular 8 without building ...
I don't understand why a lot of people keep their API URL root in environment.ts files! What if I want to deploy my...
Read more >Troubleshooting setup and configuration issues
Fixing a root url · Go to Jenkins > Manage Jenkins > Configure System, and locate the section titled "Jenkins Location". You should...
Read more >Stuck: understanding frontendurl/baseurl, and configuring ...
Hi, in my custom user registration theme I use baseUrl to “Back to login”, but after clicking this URL, the user is redirected...
Read more >Routing in ASP.NET Core - Microsoft Learn
Discover how ASP.NET Core routing is responsible for matching HTTP requests and dispatching to executable endpoints.
Read more >Hubl variable for website root url - HubSpot Community
I have a header that contains a logo that when clicked takes you to the homepage. The homepage is a root url ie...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@stukalin how good are you at debugging rollup builds? https://github.com/DockYard/ember-service-worker/pull/130 😄
Tried to upgrade the Ember from v3.4 to 3.5 today and received the same issue… Looking forward to see a fix