Check dot imports vs node_modules #7948
Comments
|
The code works if I rename my local file "utilities", so I think that seems to validate the name import. |
|
OK, it looks like it's some odd going on with the |
bep
added a commit
to bep/hugo
that referenced
this issue
Nov 12, 2020
This commit fixes some issues where modules in /assets share the same name as in node_modules. This was not intended, and with this commit the node_modules-components should be isolated. If you want to redefine something inside node_modules, use the `defines` option. Fixes gohugoio#7948
bep
added a commit
to bep/hugo
that referenced
this issue
Nov 12, 2020
This commit fixes some issues where modules in /assets share the same name as in node_modules. This was not intended, and with this commit the node_modules-components should be isolated. If you want to redefine something inside node_modules, use the `defines` option. Fixes gohugoio#7948
bep
added a commit
to bep/hugo
that referenced
this issue
Nov 12, 2020
This commit fixes some issues where modules in /assets share the same name as in node_modules. This was not intended, and with this commit the node_modules-components should be isolated. If you want to redefine something inside node_modules, use the `defines` option. Fixes gohugoio#7948
bep
added a commit
that referenced
this issue
Nov 13, 2020
This commit fixes some issues where modules in /assets share the same name as in node_modules. This was not intended, and with this commit the node_modules-components should be isolated. If you want to redefine something inside node_modules, use the `defines` option. Fixes #7948
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Hugo are you using (
hugo version)?Hugo Static Site Generator v0.78.1/extended darwin/amd64 BuildDate: unknown
Does this issue reproduce with the latest release?
I am compiling some js code with "js.Build"
I have a file called "util.js" which I import using
import { method } from "./util"and then I am also import the npm module "url" from "npm install url" usingimport { parse } from "url". Inside of the url module there is also an import from "./util" and it's getting resolved to my util.js module and causing crashes. This seems to indicated it's resolving modules by names and not resolved paths.The text was updated successfully, but these errors were encountered: