Hi team,
Following ticket Message "Forbidden" when trying to create a chart - #10 by morganperre
I am trying to install the last release of forest-express-sequelize@8.5.12
Unfortunately, I have some problems to install it properly.
After installing the last release, the forest-express module is missing from forest-express-sequelize/node_modules
Feature(s) impacted
I need the forest-express submodule in the dependencies of forest-express-sequelize in order to use the documented workaround for using case insensitive searches in filters.
Illustration below.
with forest-express-sequelize@8.5.11
# npm install forest-express-sequelize@8.5.11
+ forest-express-sequelize@8.5.11
added 19 packages from 26 contributors, updated 1 package, moved 2 packages and audited 775 packages in 8.263s
...
# ls node_modules/forest-express-sequelize/node_modules/
'@babel'/ core-js/ inherits/ jsonapi-serializer/ one-time/ semver/ winston/
async/ forest-express/ ipaddr.js/ lodash/ readable-stream/ string_decoder/
bluebird/ http-errors/ is-stream/ moment-timezone/ safe-buffer/ uuid/
forest-express
is present in node_modules
subfolder of forest-express-sequelize
with forest-express-sequelize@8.5.12
# npm install forest-express-sequelize@8.5.12
+ forest-express-sequelize@8.5.12
removed 19 packages, updated 1 package, moved 2 packages and audited 756 packages in 5.124s
...
# ls node_modules/forest-express-sequelize/node_modules/
'@babel'/ bluebird/ core-js/ depd/ http-errors/ lodash/ semver/ setprototypeof/
forest-express
is NOT present in node_modules
subfolder of forest-express-sequelize
I have no idea why this occurs.
Context
Here is my current setup:
- Project name: MyPocket
- Environment name: Development
Before the upgrade
"meta": {
"liana": "forest-express-sequelize",
"liana_version": "8.5.11",
"stack": {
"database_type": "multiple",
"engine": "nodejs",
"engine_version": "14.17.0" (npm 6.14.13)
"orm_version": "5.22.3"
}
}
I cannot start the server with upgraded release because of the missing dependency.
I also tested with nodejs 14.20.0 (npm 6.14.17), but I had the same issue.
Thanks in advance
Louis-Marie