You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When bundling folder/script2.ts (from inside folder) rollup should be able to understand that import {helloWorld} from '../script1' refers to ../script1.ts, and bundle it with no errors.
Actual Behavior
I get this error:
[!] RollupError: Could not resolve "../script1" from "script2.ts"script2.ts at getRollupError (/home/projects/stackblitz-webcontainer-api-starter-751pte/folder/node_modules/rollup/dist/shared/parseAst.js:282:41) at Object.error (/home/projects/stackblitz-webcontainer-api-starter-751pte/folder/node_modules/rollup/dist/shared/parseAst.js:278:42) at ModuleLoader.handleInvalidResolvedId (/home/projects/stackblitz-webcontainer-api-starter-751pte/folder/node_modules/rollup/dist/shared/rollup.js:20000:36) at eval (/home/projects/stackblitz-webcontainer-api-starter-751pte/folder/node_modules/rollup/dist/shared/rollup.js:19960:26)
Additional Information
This problem does not acre:
When folder/script2.ts and script1.ts are in the same folder.
When the project root (i.e. the package.json) is in / and not /folder.
When using javascript files instead of typescript ones.
When importing ../script1.ts instead of ../script1 or ../script1.js (though typescript's compiler is not happy about that, you have to enable allowImportingTsExtensions in the tsconfig)
For all of these reasons I believe that this is a bug and not an intended feature.
The text was updated successfully, but these errors were encountered:
Expected Behavior
When bundling
folder/script2.ts
(from insidefolder
) rollup should be able to understand thatimport {helloWorld} from '../script1'
refers to../script1.ts
, and bundle it with no errors.Actual Behavior
I get this error:
Additional Information
This problem does not acre:
folder/script2.ts
andscript1.ts
are in the same folder.package.json
) is in/
and not/folder
.../script1.ts
instead of../script1
or../script1.js
(though typescript's compiler is not happy about that, you have to enableallowImportingTsExtensions
in the tsconfig)For all of these reasons I believe that this is a bug and not an intended feature.
The text was updated successfully, but these errors were encountered: