-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: increase version to 0.8.2 and fix TD&TM dependency issues #765
chore: increase version to 0.8.2 and fix TD&TM dependency issues #765
Conversation
set/fix TS definitions to - "wot-thing-description-types": "1.1.0-09-February-2022" - "wot-thing-model-types": "1.1.0-3-February-2022"
Updating dependencies cause issues again for OPCUA
|
I'm looking into this |
@danielpeintner what is the version of node and and the version of npm that you are using to update the package-lock.json file ? |
On my side I am using
I have deleted the package-lock.json file and run As a consequence the package-lock.log file looks different that the one which is produce by your toolset. But also all test passes ! Can you describe the process you went through step by step to upgrade the package and the version of your tools ? |
node v16.11.1 |
Did you remove all |
Good point, |
@danielpeintner , this prob puzzled me most of the day I finally found the route cause the problem, Let me describe the situation, imagine an nodejs module
The fix is to run the layout becomes:
So the pattern to safely restore the package-lock.json file could be
|
* Publishing on NPM * Regenerating package-lock.json
@erossignon thanks for your explanation. I updated the PR accordingly and also added some information in README. |
Is this process a one-time fix or do we need it to do it every time we install/update dependencies? |
My understanding is that this is always necessary. But I let @erossignon confirm. |
yes, using |
So even when I |
|
@relu91 are you okay with proceeding and merging this PR? |
yes, let's go. |
set/fix TS definitions to