-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Relative import path not prefixed #21440
Comments
Can you share configuration files (Deno.json/package.json) and/or import mao files you have in your repository? |
Can you share configuration files (Deno.json/package.json)
This is the package.json in the folder I'm trying to run:
```
{
"name": "manga-ui",
"version": "0.0.0",
"private": true,
"scripts": {
"serve": "vite",
"build": "vue-cli-service build",
"lint": "vue-cli-service lint",
"start-backend": "nodemon --watch backend --exec ts-node
backend/index.ts",
"dev": "concurrently \"npm run serve\" \"npm run start-backend\"",
"note": "run the dev environment by typing npm run dev"
},
"dependencies": {
***@***.***/font": "7.0.96",
***@***.***/express": "^4.17.21",
"adm-zip": "^0.5.10",
"core-js": "^3.29.0",
"file-type": "^18.7.0",
"glob": "^10.3.10",
"read-chunk": "^4.0.3",
"roboto-fontface": "*",
"sequelize": "^6.35.1",
"sqlite3": "^5.1.6",
"tar": "^6.2.0",
"ts-node": "^10.9.1",
"tsc": "^2.0.4",
"tsx": "^4.6.2",
"unrar": "^0.2.0",
"unzipper": "^0.10.14",
"vue": "^3.2.0",
"vue-router": "^4.0.0",
"vuetify": "^3.0.0"
},
"devDependencies": {
***@***.***/types": "^7.21.4",
***@***.***/node16": "^16.1.1",
***@***.***/node": "^18.19.1",
***@***.***/sequelize": "^4.28.19",
***@***.***/plugin-vue": "^4.0.0",
***@***.***/cli-service": "^5.0.8",
***@***.***/eslint-config-typescript": "^11.0.0",
"eslint": "^8.22.0",
"eslint-plugin-vue": "^9.3.0",
"sass": "^1.60.0",
"typescript": "^5.3.2",
"unplugin-fonts": "^1.0.3",
"vite": "^4.2.0",
"vite-plugin-vuetify": "^1.0.0",
"vue-tsc": "^1.2.0"
}
}
```
and/or import mao files you have in your repository?
not sure what a mao file is (and Google wasn't very helpful about that)
|
I meant "import map" :) |
I don't think I have any of those, unless I'm missing something.
…On Sun, Dec 3, 2023 at 1:35 PM Bartek Iwańczuk ***@***.***> wrote:
not sure what a mao file is (and Google wasn't very helpful about that)
I meant "import map" :)
—
Reply to this email directly, view it on GitHub
<#21440 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2SFJNEXGNQZWFLTQKDZ3YHRWXZAVCNFSM6AAAAABAEPKVA6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGQ3DONRQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
勇気とユーモア
|
Experiencing this after an upgrade to deno 1.39.1, which no longer has support for import maps (I think). Error started occurring after changing from import maps -> content in root level deno.json file. |
Sorry, I closed the wrong issue. |
@codingiswhyicry see issue #23057 for that one, which is unrelated to this (it's fixed now) |
Thanks so much :-) |
@arthurwolf I tried running that code sample and there's a lot of missing dependencies not defined in the package.json like cors, multer, express. When I try to run: import { Extract as Unrar } from 'unrar';
console.log("z"); With a package.json like: {
"dependencies": {
"unrar": "^0.2.0"
}
} I get:
Looking at that package, it doesn't seem to provide an Would you be able to provide a fully reproducible example of the error you're encountering? (an example without redactions that anyone could run easily to reproduce the problem?) |
I am getting this also when importing in the REPL, the cause is importing a node-style module from outside of it's package, i.e. if we have:
If while in
The error doesn't happen with |
Version: latest
After a full day banging my head against walls trying to get ESM to work and failing, somebody recommended I try deno.
I just tried, and it does this:
which is weird that it would fail like this, thinking unrar is a relative import when it seemingly had no problem with the 10 other modules before that:
what's going on here?
thanks
The text was updated successfully, but these errors were encountered: