Oxooxo
Uncaught (in promise) TypeError: Reflect.getMetadata is not a function
I'm still trying to get it run and so I tried to understand what is going on.
First of all the error message comes from the index.js
in
/Users/me/Library/Caches/deno/npm/registry.npmjs.org/typedi/0.10.0/cjs
see (https://docs.typestack.community/typedi/develop/01-getting-started)
To use TypeDI you need to
npm install typedi reflect-metadata
in :deno_logo: :
deno install npm:typedi
Add npm:typedi@0.10.0
deno install npm:reflect-metadata
Add npm:reflect-metadata@0.2.2
Also using it in my .ts file with
import "reflect-metadata";
now works. But still I get the message
error: Uncaught (in promise) TypeError: Reflect.getMetadata is not a function
3 replies
How to get problems solved
Still feeling concrete shoes - but back to possible solutions.
I guess (hope) some people (with a lot of experience) had a look on the posts here.
It would be nice if they could write just a scentence if something goes deep and has no easy answer.
Maybe it is then a better way to open a ticket on https://github.com/denoland
Sorry if this is not much help! Just an observation!Totaly fine. I’m glad that I get some feedback 😉
4 replies
How to get problems solved
Thanks @raunioroo for your quick response.
First, a disclaimer - I'm not completely certain what DTO's are, or even Reflection in this context, just a hunch. But anyway:Maybe these two help to understand the background a bit: https://medium.com/@yelinliu/dto-explained-in-nestjs-3a296498d77b https://stackoverflow.com/questions/59397687/what-is-the-purpose-of-a-data-transfer-object-in-nestjs
Looking at your two open posts, they don't look particularly simple transfers though. Reflection and GYP related things seem to me like pretty involved stuff that are heavily linked with node internals.I did not plan to use heavily linked internals. 😉 In the DTO case I import some common used libs import { validate } from "npm:class-validator@0.14.1"; import { plainToClass } from "npm:class-transformer@0.5.1"; class-validator and class-transformer have around 3M downloads per week, that are not niche modules. I’m not involved in deeper node or deno stuff, so how should I (or others that want to change) know that this or that module does heavy stuff under the hood where deno is not yet prepared for? For the other case where I need to use the npm:xsd-validator. I could imagine that it is more complicated, because it forces to install the libxmljs deno install --allow-scripts=npm:libxmljs@1.0.11 I would also be glad if there would be a deno xsd-validator (mabe on deno.land or jsr) . I found https://deno.land/x/schema_validator@v0.0.3 4 years old and the documentation is „Free software,hell ya.“ There was an other post where I wanted to use globSync as descibed here https://docs.deno.com/api/node/fs/~/globSync It’s just not there. https://github.com/denoland/deno/issues/26927 Got no feedback here in the help channel and decided to take an other aproach by using deno Walk https://docs.deno.com/examples/walking_directories/ and deleted the post.
4 replies