Google analytics doesn't work with NueJS #175

goblinfactory · 2024-01-22T09:52:34Z

I can't find any way to add GA to a NueJS website/blog.

I've tried three approaches

Tried adding it to the <head> element.
Tried adding it at the top of the <main> in a raw <script> tag.
Lastly, I tried following instructions on controlling layout yourself, and defining the entire root layout from <html> as described here : https://nuejs.org/docs/concepts/layout-components.html#root-layout

All three approaches just crash with unexpected token error.
I'm hoping I've done simply obviously wrong.

The text was updated successfully, but these errors were encountered:

nobkd · 2024-01-22T10:37:47Z

Is unexpected token error the only thing you get, or is the error more verbose?

If possible, could you also try to provide some (redacted) snippet that represents your GA code?

nobkd · 2024-01-22T10:43:06Z

I searched around and found this example code:

<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());

gtag('config', 'G-XXXXXXX');
</script>

And got this error:

!! parse error layout.html
89 | 
90 | 
91 | // exec('`font-size:${_.size + "px"}`;', data)
92 | export function exec(expr, data={}) {
93 |   const fn = new Function('_', 'return ' + expr)
94 |   const val = fn(data)
     ^
SyntaxError: Unexpected token '.'. Expected a ';' following a class field.
      at <parse> (:5:1)
      at Function (native:1:1)
      at exec (/home/username/.bun/install/global/node_modules/nuejs-core/src/fn.js:94:23)
      at createComponent (/home/username/.bun/install/global/node_modules/nuejs-core/src/render.js:290:25)
      at map (:1:11)
      at /home/username/.bun/install/global/node_modules/nuekit/src/site.js:200:24

Which seems like the code is tried to be parsed as Nue component or something?

Edit:

Yep. I'm sure (at least for me): I added a console.log(expr) in my local installation to the beginning of this function:

nue/packages/nuejs/src/fn.js

Lines 92 to 96 in 83e96ac

    
           export function exec(expr, data={}) { 
        
             const fn = new Function('_', 'return ' + expr) 
        
             const val = fn(data) 
        
             return val == null ? '' : isJS(val) ? val : '' + val 
        
           }

And I this when running the dev server:

class Impl { 

    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());

    gtag('config', 'G-XXXXXXX');
     }

goblinfactory · 2024-01-22T10:48:40Z

@nobkd Txs for that, I was just about to add that. Yes, that's exactly the error I get.
Do you not have Google Analytics installed yourself?
i.e. are we talking about just one problem that my blog has, because you got it working easily, or a problem that we can quickly confirm impacts everyone?

goblinfactory · 2024-01-22T10:51:20Z

Just thinking about it, we might probably be able to quickly hack it by simply moving the second piece of hard coded script into another file and import that as well?

But I dont want to do any further experimenting until I've established whether it works out of the box for anyone else. Otherwise I could be trying to fix a problem that is a side effect of something else.

goblinfactory · 2024-01-22T11:01:23Z

@nobkd Yeah, I tried manually adding it to and Nue just strips it out. Not sure what the render (transform) code in Nue looks like; i assume the blog gets converted to metadata and then rendered; I'm assuming there's no transform to pick up custom GA or script tags and add that to the meta data to make it into the final rendering. Just my initial thoughts.

Here's what I tried;

Both the two lines I added have no impact on any output.

fritx · 2024-01-23T04:11:57Z

Actually I ran into problems like this too. Do we have workaround supporting inline <script> and <style> without going into expression parsing errors?

tipiirai · 2024-01-23T04:35:04Z

This is a bug on the template engine, which treats <script> tags as a special case. Need to fixt this. It's important. Thanks guys.

tipiirai · 2024-01-23T07:41:56Z

Pushed out a new Nue JS/Nuekit versions (0.3.1 and 0.3.2) where this issue is resolved. When a script tag has any attribute, such as type it is passed for the client as is. For example:

<!-- Google Analytics -->
<script type="text/javascript">
  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
  m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
  })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');

  ga('create', 'TAG_ID', 'auto');
  ga('send', 'pageview');
</script>

You can alternatively use a client attribute which passes the script for the client as is and also removes the attribute so that the HTML stays clean. ie.

<script client>
  // hey
</script>

Gets rendered as

<script>
  // hey
</script>

tipiirai · 2024-01-23T08:47:48Z

Added docs for this.

goblinfactory · 2024-01-23T16:34:47Z

the docs link above is to localhost : actual link to docs is : https://nuejs.org/docs/reference/template-syntax.html#client-side-script-tags

goblinfactory · 2024-01-23T16:48:21Z

@tipiirai
I can't get that to work;
I ran bun install nuekit@latest --global
running nue --version confirms ✓ Nue 0.3.2 • Bun 1.0.22
however, manually running nue build -r blog and then eyeballing the .dist folder, confirms we still have old version .031 see screenshot below

I manually created another starter blog

md upgrade
cd upgrade
bun create nue@latest

I then manually ran a build, nue build
and then did a file compare of the generated files, they look identical

Finally I edited the starter blog template for the brand new getting started nuejs, version 0.32, and added this to the default layout.html

<main>
  <script client>
    alert('hello')
  </script>
  <slot for="content"/>
  <blog-posts :posts/>
</main>

After adding that, and saving. I run nue build and I now get the following errors

 nue build 

✓ Nue 0.3.2 • Bun 1.0.22 
✓ Building site to: ./.dist/dev

✓ Processing styles 4
   home.css
   posts/post.css
   global/global.css
   global/feedback.css

✓ Transpiling components 1
   global/feedback.nue

✓ Generating pages 4
!! parse error layout.html
1 | export default "native";
    ^
SyntaxError: Unexpected string literal 'hello'. Expected a parameter pattern or a ')' in parameter list.
      at <parse> (:4:1)
      at Function (native:1:1)
      at exec (/Users/alanhemmings/.bun/install/global/node_modules/nuejs-core/src/fn.js:94:23)
      at createComponent (/Users/alanhemmings/.bun/install/global/node_modules/nuejs-core/src/render.js:290:25)
      at map (:1:11)
      at /Users/alanhemmings/.bun/install/global/node_modules/nuekit/src/site.js:200:24
      at processTicksAndRejections (:61:39)

   posts/scaleable-design-system.md
!! parse error layout.html
1 | export default "native";
    ^
SyntaxError: Unexpected string literal 'hello'. Expected a parameter pattern or a ')' in parameter list.
      at <parse> (:4:1)
      at Function (native:1:1)
      at exec (/Users/alanhemmings/.bun/install/global/node_modules/nuejs-core/src/fn.js:94:23)
      at createComponent (/Users/alanhemmings/.bun/install/global/node_modules/nuejs-core/src/render.js:290:25)
      at map (:1:11)
      at /Users/alanhemmings/.bun/install/global/node_modules/nuekit/src/site.js:200:24
      at processTicksAndRejections (:61:39)

   posts/color-strategies.md
!! parse error layout.html
1 | export default "native";
    ^
SyntaxError: Unexpected string literal 'hello'. Expected a parameter pattern or a ')' in parameter list.
      at <parse> (:4:1)
      at Function (native:1:1)
      at exec (/Users/alanhemmings/.bun/install/global/node_modules/nuejs-core/src/fn.js:94:23)
      at createComponent (/Users/alanhemmings/.bun/install/global/node_modules/nuejs-core/src/render.js:290:25)
      at map (:1:11)
      at /Users/alanhemmings/.bun/install/global/node_modules/nuekit/src/site.js:200:24
      at processTicksAndRejections (:61:39)

   posts/class-naming-strategies.md
!! parse error layout.html
1 | export default "native";
    ^
SyntaxError: Unexpected string literal 'hello'. Expected a parameter pattern or a ')' in parameter list.
      at <parse> (:4:1)
      at Function (native:1:1)
      at exec (/Users/alanhemmings/.bun/install/global/node_modules/nuejs-core/src/fn.js:94:23)
      at createComponent (/Users/alanhemmings/.bun/install/global/node_modules/nuejs-core/src/render.js:290:25)
      at map (:1:11)
      at /Users/alanhemmings/.bun/install/global/node_modules/nuekit/src/site.js:200:24
      at processTicksAndRejections (:61:39)

   index.md

✓ Copying static files 20
 ... redacted to save space ...
   img/twitter.svg

Time taken: 46ms

➜  upgrade git:(main) ✗

goblinfactory · 2024-01-23T16:49:18Z

Is there something else I have to do, to get access to or get started with the @latest ?
I think this ticket should remain open. I'm still able to reproduce the bug, starting from scratch, using steps above, and cannot reproduce the fix.

nobkd · 2024-01-24T13:26:37Z

confirms we still have old version .031 see screenshot below

The version-check wasn't updated in the code: https://github.com/nuejs/nue/blob/master/packages/nuekit/src/init.js#L21-L28

I run nue build and I now get the following errors

That's so weird. For me, it just works... Tested with v0.3.2 and v0.3.3...

goblinfactory · 2024-01-24T13:43:44Z

@nobkd
If I do the following

Create a new empty folder, called test32, cd test32
run nue --version observe you are running 0.3.2, bun, 1.0.22
run nue press enter. (with no parameters)

I now see the following

Questions

Shouldn't .dist/dev/@nue/.031 be /0.32?
If yes, then this explains the bug.
If no, then is are my steps to reproduce in the notes further above correct?

nobkd · 2024-01-24T14:57:49Z

Shouldn't .dist/dev/@nue/.031 be /0.32?

No, because the version check file name has not been updated in the source code. See my last comment: #175 (comment)

It's the same file structure as yours.

Open to see file structure:

My commands for a small example:

mkdir test32 && cd test32
bun create nue@latest
- Dirname: .
- Select e.g.: Simple blog
sed -i "s/<main>/<main><script client>alert('hello')<\/script>/" layout.html
- Just to have a simple example <script>
nue
Open page in browser

Open to see command line example:

goblinfactory · 2024-01-24T16:17:19Z

@nobkd Your steps are basically the same as mine. But to be extra sure I ran your exact steps, and didn't get an alert, and F12 shows no <script> element.

This could be a bun/package issue;

--- clippy says ---

It sounds like you're encountering an issue where the bun create nue@latest command is not installing the latest version of 'nue'. This could be due to a few reasons:

Cache Issue: Sometimes package managers cache an older version. Try clearing the cache.
Package Publishing Delay: The latest version might not be properly published or recognized by the package registry yet.
Version Tagging Issue: The 'latest' tag might not be correctly assigned to the newest version in the registry.
To troubleshoot:

Check the registry directly (like npmjs.com if 'nue' is an npm package) to see the latest version.
Try installing a specific version instead of using @latest.
Look for any open issues or documentation on 'bun' or 'nue' that might address this problem.

I will investigate further in a few hours. Just in the middle of some work stuff I have to complete first.

Looks like a good excuse to build that Cloudflare CICD build step, which basically will just be something like

npm install bun
bun install nue@latest
nue build -r --production
etc etc ...

Then I can test it on clean build image. If that works, then I just have to ask clippy how to clear my bun caches etc on my dev box. If it doesnt work on a clean build agent, then it could be one of the other problems mentioned by clippy.

tipiirai · 2024-01-25T06:54:28Z

Can you check from node_modules that you are using nuejs-core v0.3.1, where this issue was fixed?

goblinfactory · 2024-01-25T10:49:11Z

I'm not using any packages or node modules. I dont have a packages.json file in my project.
I'm only using nue as per the getting started docs, i.e. as a global command line tool, installed globally.
I'm currently checking-in the .dist folder to git, and not using a build step on the cloudflare server so that the deployed site is ACTUALLY the exact site I debug and build locally. (it's a hack, but it works well.)
When I run my fake make script, it calls nue build -r blog --production, then it checks in the built artifacts to git, which then triggers a cloudflare push of content to edge.

I check the version of nue that is being used by calling nue -v, which returns ✓ Nue 0.3.2 • Bun 1.0.22
It might be useful to have nue embed the version of nue in the web headers, and you can later default that to false with an option to include (if people want their dev tools to be private, which I would respect, but for early stage, having this there could be very helpful in situations like this.)

i.e. some bizarre situation where calling from command line nue -v returns version X, but running makefile uses version Y.

goblinfactory · 2024-01-25T11:31:05Z

@tipiirai Actually, here's a simpler demo of the problem.

step 1; add in the script tag to template.html
step 2: run nue build

That's it, that's all you need to do, to see the bug; here's what I get, and you can clearly see the version of nue that is running via the console output, as well as the parsing error unexpected literal string 'hello' we would expect not to see.

tipiirai · 2024-01-26T06:31:06Z

For some reason you don't have the latest nuejs-core as the dependency, which would fix the above issue. Maybe try bun install on the local install directory.

goblinfactory · 2024-01-26T10:41:08Z

... then why does Nue report version 0.3.2 when I run build?

I've perhaps misunderstood you. What exactly do you mean by nuejs-core; remember I' m just a user of an executable called Nue, (from my perspective as a new user simply using the tool and following the getting started instructions)
I'm not a team developer, and have no exposure to the innards of the nue architecture. (not yet at least)

goblinfactory · 2024-01-26T11:08:47Z

Using bun package manager and running bun install nue@latest doesnt change anything, see below.
In this screenshot you can see

nue version running
error message
package.json created by bun install nue@latest

goblinfactory · 2024-01-26T11:19:55Z

@tipiirai damn, answer is right there...

bun install nue <-- instead of --> bun install nuekit
Doh!!!
testing now...
p.s. at least I can haz nice async control flow if I wanted! 🤕😆

goblinfactory · 2024-01-26T11:27:57Z

here's the problem I think

I suspect by naming the executable nue and making the name of the tool different from the name of the package
by having --global in your getting started

Now, if at any time in the future, perhaps 3 months from now a user needs a new feature because it's all moved on quite a bit, then lets say 90% of the users look at their command line, and think .. .I need to update "nue"... yknow, that command /utility I keep running.
So they run bun install nue@latest
which it does
now when they run nue, it keeps on using nue from the first gloally installed nuekit package.

Options / suggestions to fix

Change the documentation to NEVER EVER suggest installing it globally. Or this problem will happen for a certain % of users and create a support burden and or lose users
Rebrand the command line tool to Nuejs or nuekit or something, and align the package name exactly with the command line name.
other...? (dunno, to be discussed)

goblinfactory · 2024-01-26T11:37:32Z

@tipiirai
Just finished testing; Sadly running bun install nuekit@latest and using local packages, does not fix the problem. See screenshot. I will test next on clean build machine with Cloudflare build agent.

goblinfactory · 2024-01-26T15:52:14Z

works flawlessly on Cloudflare build agent with bun & npx

@tipiirai here's some more pieces to the puzzle;
I started a new project from scratch, and just like above, it didn't work. But this time I created a new Cloudflare Pages project and used this very complicated build pipeline below

bun update && npx nue build --production

And configured the build output directory in Cloudflare dashboard, and it works flawlessy; ...well, fast and flawlessly! <-- I trademark that!! ...lol

that will be a great tagline, Fast and flawlessly!

I digress, ... so we know it works properly on a clean build machine, and that we have at least 1 person reporting an issue of upgrading to latest packages and dependancies, (me) and for some reason Bun is failing to update.
Here's the proof it's working;
https://fetish-pond-diving.divecode.co.uk/

This spike projects includes a cheesy alert box, just to prove that using <script client> now works.

Below is a redacted extract of the build log from Cloudflare after doing a git push on main branch.

Cloning repository...
[redacted] From [redacted]
[redacted] branch [redacted] -> FETCH_HEAD
HEAD is now at [redacted] update social
Using v2 root directory strategy
Success: Finished cloning repository files
Detected the following tools from environment: [email protected], [email protected]
Installing project dependencies: bun install --frozen-lockfile
bun install v1.0.1 ([redacted])
+ [email protected]
15 packages installed
Executing user command: bun install && npx nue build --production
Checked 15 installs across 16 packages (no changes)
bun install v1.0.1 ([redacted])
✓ Nue 0.3.3 • Bun 1.0.1
✓ Building site to: ./.dist/prod
✓ Processing styles 4
✓ Transpiling components 1
✓ Generating pages 4
✓ Copying static files 24
[ images et al]
Time taken: 140ms
Finished
Note: No functions dir at /functions found. Skipping.
Validating asset output directory
Deploying your site to Cloudflare's global network...
Uploading... (41/45)
Uploading... (43/45)
Uploading... (44/45)
Uploading... (45/45)
✨ Success! Uploaded 4 files (41 already uploaded) (0.93 sec)
✨ Upload complete!
Success: Assets published!
Success: Your site was deployed!

The build takes 140ms, and the full site deployment, including CDN cache invalidation takes a further 0.93s (930ms), excluding the time it takes for a git push to actually trigger the build, which in my experience is around 3 to 4seconds. Though that's including the full round trip of how long it takes for the web UI to receive notification, so it's obviously less than that value.

from git push on my local machine, it takes me about 7 seconds, pressing Cmd+R to see the updated site.

nobkd · 2024-01-28T17:09:15Z

Great that it at least works on other devices. +

here's the problem I think

I suspect by naming the executable nue and making the name of the tool different from the name of the package

by having --global in your getting started

I agree, that the command does not fit to the nuekit package. I also some time ago installed nue and then tried to run the nue command, which obviously failed. 😅
And I also dislike the global installation, as the packages are not properly reflected in the project's package list / information.

Change the documentation to NEVER EVER suggest installing it globally. Or this problem will happen for a certain % of users and create a support burden and or lose users
Rebrand the command line tool to Nuejs or nuekit or something, and align the package name exactly with the command line name.

On your side on both points there +

Just finished testing; Sadly running bun install nuekit@latest and using local packages, does not fix the problem

That's just really weird...
Have you tried deleting bun (rm -rf ~/.bun) and local node_modules on your machine and just reinstalling everything? 🤷

Can you share what system you are on? Like operating system (and distribution) or so?

bun update && npx nue build --production

May I ask why you use npx to run nue-command on remote instead of bunx? Or did you just use the one that came to mind first?

And configured the build output directory in Cloudflare dashboard, and it works flawlessy; ...well, fast and flawlessly! <-- I trademark that!! ...lol

lol 😂

tipiirai · 2024-01-31T07:31:51Z

Awesome work guys! I'm thinking of bundling Nue JS server components inside Nuekit later so that Nue JS only consists of client-side reactive parts. Nue JS is super buggy atm, and I think we should offer React (maybe Svelte) alternatives for building single-page apps. Not that this would solve the Bun install issue here. Just thinking aloud.

goblinfactory · 2024-02-01T21:02:34Z

@tipiirai I have Google Analytics working on my blog using the latest NueJs. closing,
txs for the quick responses.

tipiirai self-assigned this Jan 23, 2024

tipiirai added the bug label Jan 23, 2024

tipiirai closed this as completed in b4a476b Jan 23, 2024

tipiirai reopened this Jan 25, 2024

nobkd mentioned this issue Jan 29, 2024

The code in the script tag was mistakenly executed as a property error #183

Closed

goblinfactory closed this as completed Feb 1, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Google analytics doesn't work with NueJS #175

Google analytics doesn't work with NueJS #175

goblinfactory commented Jan 22, 2024 •

edited

Loading

nobkd commented Jan 22, 2024 •

edited

Loading

nobkd commented Jan 22, 2024 •

edited

Loading

goblinfactory commented Jan 22, 2024 •

edited

Loading

goblinfactory commented Jan 22, 2024

goblinfactory commented Jan 22, 2024

fritx commented Jan 23, 2024

tipiirai commented Jan 23, 2024

tipiirai commented Jan 23, 2024

tipiirai commented Jan 23, 2024

goblinfactory commented Jan 23, 2024

goblinfactory commented Jan 23, 2024

goblinfactory commented Jan 23, 2024 •

edited

Loading

nobkd commented Jan 24, 2024

goblinfactory commented Jan 24, 2024

nobkd commented Jan 24, 2024

goblinfactory commented Jan 24, 2024 •

edited

Loading

tipiirai commented Jan 25, 2024

goblinfactory commented Jan 25, 2024 •

edited

Loading

goblinfactory commented Jan 25, 2024 •

edited

Loading

tipiirai commented Jan 26, 2024

goblinfactory commented Jan 26, 2024 •

edited

Loading

goblinfactory commented Jan 26, 2024

goblinfactory commented Jan 26, 2024 •

edited

Loading

goblinfactory commented Jan 26, 2024

goblinfactory commented Jan 26, 2024

goblinfactory commented Jan 26, 2024 •

edited

Loading

nobkd commented Jan 28, 2024 •

edited

Loading

tipiirai commented Jan 31, 2024

goblinfactory commented Feb 1, 2024

Google analytics doesn't work with NueJS #175

Google analytics doesn't work with NueJS #175

Comments

goblinfactory commented Jan 22, 2024 • edited Loading

nobkd commented Jan 22, 2024 • edited Loading

nobkd commented Jan 22, 2024 • edited Loading

goblinfactory commented Jan 22, 2024 • edited Loading

goblinfactory commented Jan 22, 2024

goblinfactory commented Jan 22, 2024

fritx commented Jan 23, 2024

tipiirai commented Jan 23, 2024

tipiirai commented Jan 23, 2024

tipiirai commented Jan 23, 2024

goblinfactory commented Jan 23, 2024

goblinfactory commented Jan 23, 2024

goblinfactory commented Jan 23, 2024 • edited Loading

nobkd commented Jan 24, 2024

goblinfactory commented Jan 24, 2024

Questions

nobkd commented Jan 24, 2024

goblinfactory commented Jan 24, 2024 • edited Loading

tipiirai commented Jan 25, 2024

goblinfactory commented Jan 25, 2024 • edited Loading

goblinfactory commented Jan 25, 2024 • edited Loading

tipiirai commented Jan 26, 2024

goblinfactory commented Jan 26, 2024 • edited Loading

goblinfactory commented Jan 26, 2024

goblinfactory commented Jan 26, 2024 • edited Loading

goblinfactory commented Jan 26, 2024

goblinfactory commented Jan 26, 2024

goblinfactory commented Jan 26, 2024 • edited Loading

works flawlessly on Cloudflare build agent with bun & npx

nobkd commented Jan 28, 2024 • edited Loading

tipiirai commented Jan 31, 2024

goblinfactory commented Feb 1, 2024

goblinfactory commented Jan 22, 2024 •

edited

Loading

nobkd commented Jan 22, 2024 •

edited

Loading

nobkd commented Jan 22, 2024 •

edited

Loading

goblinfactory commented Jan 22, 2024 •

edited

Loading

goblinfactory commented Jan 23, 2024 •

edited

Loading

goblinfactory commented Jan 24, 2024 •

edited

Loading

goblinfactory commented Jan 25, 2024 •

edited

Loading

goblinfactory commented Jan 25, 2024 •

edited

Loading

goblinfactory commented Jan 26, 2024 •

edited

Loading

goblinfactory commented Jan 26, 2024 •

edited

Loading

goblinfactory commented Jan 26, 2024 •

edited

Loading

nobkd commented Jan 28, 2024 •

edited

Loading