2026-10-20 10:49
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@element-plus/icons-vue"
node_modules/element-plus/es/components/table-v2/src/components/sort-icon.mjs:3:33:
3 │ import { SortUp, SortDown } from '@element-plus/icons-vue';
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@element-plus/icons-vue"
node_modules/element-plus/es/components/upload/src/upload-list2.mjs:3:68:
3 │ import { Document, CircleCheck, Check, Close, ZoomIn, Delete } from '@element-plus/icons-vue';
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@floating-ui/dom"
node_modules/element-plus/es/components/tour/src/helper.mjs:2:88:
2 │ import { offset, flip, shift, detectOverflow, arrow, computePosition, autoUpdate } from '@floating-ui/dom';
╵ ~~~~~~~~~~~~~~~~~~
You can mark the path "@floating-ui/dom" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@element-plus/icons-vue"
node_modules/element-plus/es/components/pagination/src/components/pager.mjs:2:52:
2 │ import { DArrowLeft, MoreFilled, DArrowRight } from '@element-plus/icons-vue';
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/es/components/pagination/src/components/sizes2.mjs:2:24:
2 │ import { isEqual } from 'lodash-unified';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/es/components/time-picker/src/time-picker-com/basic-time-spinner.mjs:2:25:
2 │ import { debounce } from 'lodash-unified';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@popperjs/core"
node_modules/element-plus/es/components/select/src/select.mjs:1:27:
1 │ import { placements } from '@popperjs/core';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "@popperjs/core" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/es/utils/arrays.mjs:1:41:
1 │ export { castArray as ensureArray } from 'lodash-unified';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/es/components/cascader-panel/src/store.mjs:1:24:
1 │ import { isEqual } from 'lodash-unified';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@element-plus/icons-vue"
node_modules/element-plus/es/components/message-box/src/index.mjs:6:24:
6 │ import { Loading } from '@element-plus/icons-vue';
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/es/components/tooltip-v2/src/tooltip2.mjs:2:21:
2 │ import { pick } from 'lodash-unified';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@element-plus/icons-vue"
node_modules/element-plus/es/components/cascader-panel/src/menu.mjs:3:24:
3 │ import { Loading } from '@element-plus/icons-vue';
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@element-plus/icons-vue"
node_modules/element-plus/es/components/select/src/select.mjs:2:39:
2 │ import { CircleClose, ArrowDown } from '@element-plus/icons-vue';
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/lib/components/color-picker/src/color-picker2.js:5:28:
5 │ var lodashUnified = require('lodash-unified');
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle. You can also surround this
"require" call with a try/catch block to handle this failure at run-time instead of bundle-time.
X [ERROR] Could not resolve "@element-plus/icons-vue"
node_modules/element-plus/lib/components/collapse/src/collapse-item.js:5:23:
5 │ var iconsVue = require('@element-plus/icons-vue');
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle. You can also surround this
"require" call with a try/catch block to handle this failure at run-time instead of bundle-time.
X [ERROR] Could not resolve "@element-plus/icons-vue"
node_modules/element-plus/lib/components/button/src/button.js:5:23:
5 │ var iconsVue = require('@element-plus/icons-vue');
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle. You can also surround this
"require" call with a try/catch block to handle this failure at run-time instead of bundle-time.
X [ERROR] Could not resolve "@element-plus/icons-vue"
node_modules/element-plus/lib/components/page-header/src/page-header.js:5:23:
5 │ var iconsVue = require('@element-plus/icons-vue');
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@element-plus/icons-vue" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle. You can also surround this
"require" call with a try/catch block to handle this failure at run-time instead of bundle-time.
X [ERROR] Could not resolve "normalize-wheel-es"
node_modules/element-plus/lib/directives/mousewheel/index.js:5:29:
5 │ var normalizeWheel = require('normalize-wheel-es');
╵ ~~~~~~~~~~~~~~~~~~~~
You can mark the path "normalize-wheel-es" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle. You can also surround this
"require" call with a try/catch block to handle this failure at run-time instead of bundle-time.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/es/components/form/src/utils.mjs:2:26:
2 │ import { castArray } from 'lodash-unified';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/es/components/tree-select/src/select.mjs:2:21:
2 │ import { pick } from 'lodash-unified';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/es/components/tree-select/src/tree.mjs:2:37:
2 │ import { pick, isEqual, isNil } from 'lodash-unified';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "lodash-unified"
node_modules/element-plus/es/components/virtual-list/src/hooks/use-cache.mjs:2:24:
2 │ import { memoize } from 'lodash-unified';
╵ ~~~~~~~~~~~~~~~~
You can mark the path "lodash-unified" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
2026-09-21 10:19
续上
4.Master库中的ACT_GE_BYTEARRAY表的升级
这个表的升级需要单独说,因为这次升级过程中这个表造成的困扰最大
1.首先这个表通过navicat进行数据差异化比较,能正常生成差异化sql,但是这个表里面有个Blob字段,该字段是二进制,sql中该字段被转成了十六进制,导致超出了数据库的sql长度,被截断无法正常插入
2.后面我又采用达梦的dexp、dimp的命令的表方式进行导出导入,可能是达梦的版本差异,dimp无法使用表格的增量数据导入,导致导入的时候有主键冲突
3.然后我只能删除生产库的ACT_GE_BYTEARRAY表,因为这个表是引擎的通用依赖表,表上面有很多级联关系,导致我只能删除该表和级联关系,才将这个表导入成功,但是级联关系不能自动创建,也没有梳理清楚里面哪些表与这个表有级联关系,导致无法重建这些级联关
4.最后我就只能把所有ACT_前缀表都删除,然后通过达梦迁移工具,将ACT_前缀的表重新迁移
问题:这个表的迁移过程简直是痛苦,并且现在是因为生产上还没有产生运行数据,否则后面无法升级,因为ACT_RU表也会与ACT_GE_BYTEARRAY表有级联关系,导致以后无法直接删除ACT_前缀的所有表?请问是否有更好的升级方案