Some helpful hints to syntax errors, notably as related to 'npm run build' and 'firebase deploy' as related to syntax error shows either an older version a 'build/static/js/mainxxxxx.js' build or a current version but seems to be referencing an older version of this.
1. Updating the 'index.html' file on new deployment. Important to do this. You can add a space in the file (or some character which makes the operation of the file functionally unchanged), for instance.
2. In the Firebase console under the hosting tab, you may need to rollback to the current deployment, or at least ensure this has happened. I have found that any new 'firebase deploy' command hasn't fully ensured updates of all deployment files to the latest deployment batch.
I have also experienced old cached site data remaining even upon refreshing firebase server data. I am not certain why this seems to be more so the case either with 'firebase deploy' ments or 'firebase serve' (local hosting), but with chrome browser, you can do a refresh load with ctrl+'reload'. Seems to remedy old data in the browser system.
My current experience as of 12/13/2017
1. Updating the 'index.html' file on new deployment. Important to do this. You can add a space in the file (or some character which makes the operation of the file functionally unchanged), for instance.
2. In the Firebase console under the hosting tab, you may need to rollback to the current deployment, or at least ensure this has happened. I have found that any new 'firebase deploy' command hasn't fully ensured updates of all deployment files to the latest deployment batch.
I have also experienced old cached site data remaining even upon refreshing firebase server data. I am not certain why this seems to be more so the case either with 'firebase deploy' ments or 'firebase serve' (local hosting), but with chrome browser, you can do a refresh load with ctrl+'reload'. Seems to remedy old data in the browser system.
My current experience as of 12/13/2017
No comments:
Post a Comment