I'm transferring an older project in Cypress to a new one, but somehow I don't understand it. In the older version I had tests saved in the integration folder and then ran them from there. In the new version of Cypress, everything is stored in the e2e folder and if I play the files from the old project there, they don't show up. The structure is completely different. Do you know how to migrate it correctly? I am migrating from version 6.9.0 to version 12.3.0
I will add that I am doing a completely new installation on a new machine.
I found that I had a problem in the specification. I've edited it and now everything displays correctly as it should. See picture:
Related
I have an old Rails app that I'm trying to upgrade to Rails 7. Somewhere in the upgrade process I broke the asset pipeline. When I make updates to a javascript file, the changes aren't visible unless I run rails assets:precompile and restart the server.
When I do run rails assets:precompile, I get a bunch of compiled JS and CSS assets in my public/assets folder. This seems like an outdated version of the asset pipeline process.
This project is a personal project that I've had lying around for years and it spans Rails versions from 4 to 7. It's never had a user base, it's just an idea that I go back and work on from time to time. So it's possible I have an old version of the assets pipeline running.
I created a new Rails 7 project from scratch and it works as expected. I've been trying to make the new project as close to my existing project as I can to see where my current project is breaking, but that is becoming extremely difficult and not yielding any results yet.
I'm sure I must have some old configuration still in place but I have no idea where to look. I can't remember ever having this problem before. I would love any suggestions on where to look for differences between the old broken application and the new one that works.
So this is really unsatisfying, but what finally resolved this issue was that I removed the bootsnap gem. I don't know what was happening or why, but after removing this gem, it behaved normally.
After updating to latest stable version of library ngx-masonry 14.0.0 tests failed. They had release yesterday (24.10.2022.) and here is the link to their changelog: https://github.com/wynfred/ngx-masonry/blob/master/CHANGELOG.md
Basically they added Ivy build since they were using ViewEngine on older versions. I suppose that this error is connected to that migration to newer Angular compiler. On project we use Angular version 14.
After running npm i ngx-masonry#14.0.0 update was successful without any vulnerabilities.
In order for me to test it, I run ng test for my Angular application to make sure everything is fine. The failing test is basically the basic one which tests if the component is getting created. The following error was thrown in couple of components that rely on ngx-masonry library: ReferenceError: require is not defined
Since this is quite fresh issue (<24hrs old) probably more developers will run into it when they upgrade version to 14.
Link to the issue opened right now on their GitHub repo: https://github.com/wynfred/ngx-masonry/issues/98
Maybe we are missing something or this could be solved easily. :)
The owner of the library have just released 14.0.1 version which contains the fix. After you run npm i ngx-masonry#14.0.1 everything should be fine. Tests are passing as expected and app compiles successfully.
I'm having a problem with deploying my project.
It's VueJs project, a web app, build on Metronic template with Vuetify components.
When I publish, I use visual studio code with npm run build and upload the dist folder to my server.
I have a version-check problem.
Some of my clients cannot get the latest version, without hard reloading. ctrl-shift-r they are using chrome and when incognito mode is on everything is perfect. But normal mode brings a very old version of the app.
I need a solution on the code or server-side, thank you for your help
I solved my problem and I forgot to post my answer. My problem was because of the PWA package I installed and implemented in the beginning of the project.
When I try to remove PWA from my project, what I did was commenting the code blocks but not removing dependency from my packacge.json.(mistake) So, I was thinkin, *"Since I'm not calling any of the PWA functions or initialize it, it should've been removed."
yeah, not.
It was still there, caching stuff.
So I removed (uninstalled) the dependency from my packacge.json, and even after that, people who did installed PWA before and "not uninstalled properly" was still using cache! (yeah, you have to click uninstall and also check remove files option)
so I had to, manually uninstalled my PWA app from their chrome (thankfully it was only few) and problem solved.
I recently upgraded to the latest version of meteor. The currently installed meteor version is Meteor 1.4.1.
In trying to continue developing my app (from the previous version) in the upgraded meteor environment, I figured I would create a new app (meteor create newApp) then copy (the code from the original app) and paste (the code into the newly created files) then run it.
I quickly released that I have to re-install the packages that my original app was depending on or else I get error messages.
The issue here is I don't remember the packages my original app is dependent on. I still have the original app folder, which I created in the previous meteor version. Is there a way to extract the list of packages from the original app?
Alternatively is there a way I can merely continue developing and running the original app without having to create a new app and copy and pasting the code? If so how do I do this?
Any help is greatly appreciated
In the app root go to ./meteor directory. In that folder open packages files. All your installed packages names will be there.
Alternatively, you can use meteor list command in the app directory.
Answer to the second part, yes you can continue developing the same app. The packages will be upgraded accordingly. You may face some issues with bcrypt if you are using accounts-passwords package but there are workaround to get over that.
I user grunt-bumper to bump up my version in the package.json file if I release my app. I have a readme.md file included as well in which the current version is also described. I am no searching for a way that grunt updates this version tag automatically each time, I release my app.
I neither have found a plugin for this nor did I find an easy way to get this to work manually..
Does anybody have a clue how this can be done easily`and nice?