Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

149
Views
Why doesn't Image().src like explicit relative paths in Node.JS

As the title says, why do Image.src() operations using explicit relative paths e.g:

    picture = new Image();
    picture.onload = function()
    {
        console.log('Loaded');
    }
    picture.src = './assets/picture.png'; // Assume directory is correct relative path

or:

    const picture = require('./assets/picture.png');  // Assume directory is correct relative path

    picture = new Image();
    picture.onload = function()
    {
        console.log('Loaded');
    }
    picture.src = picture;

Not work at all (picture.onload never loads, even though .src is assigned after it (in both cases)). But, then:

    import picture from './assets/picture.png';

    picture = new Image();
    picture.onload = function()
    {
        console.log('Loaded');
    }
    picture.src = picture;

Works perfectly fine and the onload is almost instant. I'm looking to mass-import images, therefore I'll be using:

    const pictures = importAll(require.context('./assets', false, /\.png/));

However, since explicit/require don't work, this also doesn't work. Not sure what I'm doing wrong here.

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!