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
There should be an operator.js file in the node_modules/sequelize/lib/ folder after installing sequelize.
What is actually happening?
There is an operators.ts file instead of the operator.js file in the node_modules/sequelize/lib/ folder after installing sequelize.
Additional context
Screenshot:
I am unuable to reproduce this locally though. When i git clone the sequelize repo and run npm run build it does spit out an operators.js file as you can see in this screenshot:
Actually you are correct: there is no lib/operators.js anymore. It is part of the dist directory however. I'd suggest to use the exported Op property of the sequelize object
Issue Creation Checklist
[x ] I have read the contribution guidelines
Bug Description
What do you expect to happen?
There should be an
operator.js
file in thenode_modules/sequelize/lib/
folder after installing sequelize.What is actually happening?
There is an
operators.ts
file instead of theoperator.js
file in thenode_modules/sequelize/lib/
folder after installing sequelize.Additional context
Screenshot:
I am unuable to reproduce this locally though. When i git clone the sequelize repo and run
npm run build
it does spit out anoperators.js
file as you can see in this screenshot:Also, another bit of weirdness: It shows up properly on unpkg: https://unpkg.com/browse/sequelize@6.12.0/dist/lib/operators.js and also on jsdelivr: https://cdn.jsdelivr.net/npm/sequelize@6.12.0/dist/lib/operators.js. However, if you try to download the gzipped tar from npm, the issue mentioned above is present: https://registry.npmjs.org/sequelize/-/sequelize-6.12.0.tgz
So perhaps its an issue with the tar?
I also tried running
npm cache clean --force
but after a reinstall it is still showingoperators.ts
instead ofoperators.js
.Related I think: #13731
Environment
Bug Report Checklist
How does this problem relate to dialects?
Would you be willing to resolve this issue by submitting a Pull Request?
The text was updated successfully, but these errors were encountered: