Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

createEvent fails with Deno: TypeError: (0 , ne.runes) is not a function #282

Open
greenstick opened this issue Oct 17, 2024 · 0 comments
Open

Comments

@greenstick
Copy link

As the title says. Minimum reproducible example using the arguments from the documentation (works in Deno REPL):

const { createEvent } = await import("https://esm.sh/[email protected]");
const { error, value } = createEvent({
  start: [2018, 5, 30, 6, 30],
  duration: { hours: 6, minutes: 30 },
  title: 'Bolder Boulder',
  description: 'Annual 10-kilometer run in Boulder, Colorado',
  location: 'Folsom Field, University of Colorado (finish line)',
  url: 'http://www.bolderboulder.com/',
  geo: { lat: 40.0095, lon: 105.2669 },
  categories: ['10k races', 'Memorial Day Weekend', 'Boulder CO'],
  status: 'CONFIRMED',
  busyStatus: 'BUSY',
  organizer: { name: 'Admin', email: '[email protected]' },
  attendees: [
    { name: 'Adam Gibbons', email: '[email protected]', rsvp: true, partstat: 'ACCEPTED', role: 'REQ-PARTICIPANT' },
    { name: 'Brittany Seaton', email: '[email protected]', dir: 'https://linkedin.com/in/brittanyseaton', role: 'OPT-PARTICIPANT' }
  ]
});

console.log(error);
console.log(value);

Results in the error:

TypeError: (0 , ne.runes) is not a function
    at Ut (https://esm.sh/v135/[email protected]/denonext/ics.mjs:7:3424)
    at fr (https://esm.sh/v135/[email protected]/denonext/ics.mjs:21:20)
    at o (https://esm.sh/v135/[email protected]/denonext/ics.mjs:51:8665)
    at ct (https://esm.sh/v135/[email protected]/denonext/ics.mjs:51:8849)
    at Rr (https://esm.sh/v135/[email protected]/denonext/ics.mjs:51:8347)
    at <anonymous>:2:26
null
undefined

I've looked through the code in this repo to try and trace the issue but I'm unable to find a reference to the line triggering the error. That said, looking through recent closed issues I found ones referencing the runes library (#279 and #270) – perhaps this issue is related.

In case this is an error with my code, any guidance would be tremendously appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant