Open mattjohnsonpint opened 1 year ago
To clarify, if I use --force
or --legacy-peer-deps
, it adds visitor-as
to the devDependencies
section correctly, but future calls to npm install
(such as on a fresh clone of my project repo) still fail with the same message.
As a workaround, this seems to do the trick:
{
"dependencies": {
"json-as": "^0.5.65"
},
"devDependencies": {
"assemblyscript": "^0.27.14",
"visitor-as": "^0.11.4"
},
"overrides": {
"assemblyscript": "$assemblyscript"
}
}
With that override, now my npm install
works without giving an error.
Got it. Yeah that's just how NPM works sometimes and is a problem with visitor-as' deps
Steps to reproduce:
npm run asbuild
- it should compile without errornpm install json-as
asconfig.json
to add"transform": ["json-as/transform"]
to the existingoptions
sectionnpm run asbuild
again - it fails with:Tried manually installing with
npm install visitor-as --save-dev
, but that gives:It does work if I use
--force
, but I shouldn't have to do that.Not sure if this is a problem with
as-json
, or withvisitor-as
, or both.Thanks.