question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: Automatic publicPath is not supported in this browser.

See original GitHub issue

Contact Details

No response

What happened?

Hi,

I am migrating from react-particles-js, while the trying to setup the new tsprticles, i run into this issue: Automatic publicPath is not supported in this browser

I do have to note that the old system is using requirejs and that we dont implement webpack into this system

I have both tested via Vanilla and Via React, but both times the tsparticles failes to load.

When i dis into the code i see that you try to check to load the script tags and search if the script is loaded. Problem i assume is requirejs, that dynamic load the script based on the require function

Any help is welcome, as this blocks the loading of our login system, only alternative for now is or go back to old system or remove tsParticles 😦

Version

1.4.0

Which library are you using?

Vanilla (tsparticles), React.js (react-tsparticles, react-particles-js)

tsParticles Configuration

tsParticles.load("ReactParticles", {
            particles: {
                number: {
                    value: 100
                },
                color: {
                    value: "random",
                    animation: {
                        enable: true,
                        speed: 50,
                        sync: false
                    }
                },
                shape: {
                    type: "circle",
                },
                size: {
                    value: 5,
                    random: true,
                    animation: {
                        enable: true,
                        speed: 16,
                        minimumValue: 0.1,
                        sync: false
                    }
                },
                links: {
                    enable: true,
                    distance: 100,
                    color: "random",
                    opacity: 0.4,
                    width: 1
                },
                move: {
                    enable: true,
                },
            },
            interactivity: {
                detectsOn: "canvas",
                events: {
                    onHover: {
                        enable: true,
                        mode: "repulse"
                    },
                    onClick: {
                        enable: true,
                        mode: "bubble"
                    },
                    resize: true
                },
                modes: {
                    grab: {
                        distance: 400,
                        links: {
                            opacity: 1
                        }
                    },
                    bubble: {
                        distance: 400,
                        size: 40,
                        duration: 2,
                        opacity: 0.8
                    },
                    repulse: {
                        distance: 200
                    },
                    push: {
                        quantity: 4
                    },
                    remove: {
                        quantity: 2
                    }
                }
            },
            detectRetina: true,
        });

What browsers are you seeing the problem on?

No response

Relevant log output

No response

Code of Conduct

  • I agree to follow this project’s Code of Conduct

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
vmcfirecommented, Feb 5, 2022
0reactions
matteobrunicommented, Feb 18, 2022

As you close this does this mean that in the next release the issue can be fixed?

I can’t replicate the issue, I got no informations about that in days.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Webpack5 Automatic publicPath is not supported in this browser
The error is caused by a bug in mini-css-extract-plugin 1.3.8 and lower in combination ...
Read more >
Uncaught Error: Automatic publicPath is not ... - GitHub
Current Behavior Newly created application using the react preset randomly fails to load in Firefox Steps to Reproduce npx ...
Read more >
Automatic publicPath is not supported in this browser - sage
Hello, I'm using bud in sage 10 and trying to dynamic imports some scripts in my resources. When I use yarn dev, I...
Read more >
Webpack5 Automatic publicPath is not supported in this browser
at E:\maktab\Control-panel\newcontrol\final-control\node_modules\css-loader\dist\cjs.js! the error is from the font file bath in fonts.scss. @font-face { font- ...
Read more >
Uncaught Error: Automatic publicPath is not ... - WordPress.org
Uncaught Error: Automatic publicPath is not supported in this browser ... so please resolve my issue. ... Hi, and thank you for writing...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found