Closed miqmago closed 1 year ago
In node_modules/@ionic/core/dist/collection/components/modal/gestures/utils.js
/*!
* (C) Ionic http://ionicframework.com - MIT License
*/
- import { GESTURE } from '@utils/overlays';
+ import { GESTURE } from '../../../utils/overlays';
export const handleCanDismiss = async (el, animation) => {
Seems an issue with @ionic/core
but it's really strange I haven't found any issue related to this in https://github.com/ionic-team/ionic-framework @sean-perkins
@miqmago thanks for reporting this issue!
I have an open PR that will resolve this in Ionic Framework: https://github.com/ionic-team/ionic-framework/pull/26448
Here is a dev-build in the interim: 6.4.1-dev.11670531659.1bd9a8b7
.
This issue stems from using Ionic Framework components (Stencil components) in another Stencil library/app. We occasionally have an alias import slip through, causing this issue. The team is aware and hoping to fix the root issue in Stencil in the future. If it happens again, please feel free to report an issue in Ionic Framework and we can take a look.
This bug has been fixed in Ionic Framework v6.4.1, and as such I'm going to close this issue out. Should the bug re-appear, please feel free to open a new issue. Thanks!
i have nx repo setup with 2 stencil projects side by side. One is shared project.
i am importing it in primary with shared added as dependency of primary via package.json.
now inside the dist folder
my esm.js has entries like
import { B as BUILD, c as consoleDevInfo, p as plt, w as win, H, d as doc, N as NAMESPACE, a as promiseResolve, b as bootstrapLazy } from './p-1e1c6d5d.js';
export { s as setNonce } from './p-1e1c6d5d.js';
import { g as globalScripts } from './p-bbf09086.js';
import './p-4441dfdd.js';
import '@myapp/elements-shared'; ----------> problem!
import './p-b035563c.js';
also while building get lot of warnings
Bundling Warning UNRESOLVED_IMPORT
'@myapp/elements-shared' is imported by
./src/components/transfer-element/beneficiary-add/beneficiary-add.tsx,
but could not be resolved – treating it as an external dependency
@pranav-js can you do me a favor and please open a new issue with a minimal reproduction case? Thanks!
@rwaskiewicz I will try that, my current setup is pretty complex with nx setup of (integrated and packagebased repo). both of my stencil repo I migrated to package based setup. when linked via tsconfig paths it works fine, but not when linked via package.json entry points.
Prerequisites
Stencil Version
^2.17.3
Current Behavior
I've started a new stencil app with
npm init stencil
. I've installed dependencies, and when runningnpm start
it shows a warning:When using a modal it throws an exception:
Expected Behavior
No warning should appear. Modal should be able to instantiate and show.
System Info
Code Reproduction URL
https://stenciljs.com/docs/getting-started
Additional Information
It also fails when updating to
"@ionic/core": "^6.3.9"