I'm building a project and I wanted to implement Next UI on my Next js 13 project. I'm following the next UI docs, but it doesn't work, it gives me many errors. The documentation is written for version 12 or less. As you can see _document.js fails because pages folder is now called app. Can anyone tell me how to simply integrate Next UI into my Next.js 13 project?
I tried importing exactly as the docs say, but is not being accepted. The page doesn't even render.
Here you can see docs for Next 13: https://nextui.org/docs/guide/nextui-plus-nextjs#nextjs-13
And app directory its beta. Maybe it doesnt support some features.
Related
I am using vue-full-calendar library and full calendar scheduler for displaying resources in my app. Everything worked well.The calendar shows resources and the app is running since almost two years. But the last days it is impossible to display the calendar with resources .I have everything set up and i use the same library version as the docs suggest in this code sandbox example.
After debug i notice that the scheduler plugin is not loading.I don't understand why it stop working and the library stop loading.Does anyone have an idea what's going wrong or encountered the same problem.
Thanks for your help.
EDIT:
After some checks i reinstall fullcalendar-scheduler with command : npm install --no-optional --save fullcalendar-scheduler#1.9.4 and now i've got this error in my browser console.
I'm using D3.js in an asp.net core application using Visual Studio 2019.
D3 itself works, I can create SVG charts that work as expected.
However, the intellisense for D3 when using Razor does not work.
I get the following error message,
Intellisense is unable to determine the accuracy of this completion
item
I made sure intellisese is enabled.
I have tried using referencing the D3 library locally or using a link to the CDN.
I have seen some things on this topic on previous version of Visual studio regarding a _reference.js file but that doesn't apply in vs2019.
thx in advance
Even though I am running Visual Studio 2019 v16.3.2, my D3 project was created when v16.3.0 was latest.
The intellisense in fresh projects created in v16.3.2 works perfectly even though there was nothing in the release notes that indicated any intellisense fix in Javascript.
In the end, I created a fresh new Visual Studio solution and imported my old project file by file.
I did not change a line of code or change any setting. The only difference between the two solutions is that the old one was created when v16.3.0 was latest (and upgraded to v16.3.2) and the new one when v16.3.2 is latest.
This is more of a workaround than an answer but I wasted too many hours on this and had to move on.
In nearest future I will be doing a serious update of the application. I have a little experience with ember.js & have no one who can help me resolving this matter. The app is written in ember 1.12, and there are few dependencies. It has a web version and mobile (iOS+Android) written in cordova - all of them need an upgrade.
What kind of problems should I expect?
How to prepare for them?
How much time should I estimate?
Any help will be very useful- it's first time when I will be doing app upgrade.
I have checked this links, but most of them are for above 2.0 versions.
https://www.emberscreencasts.com/meta_guide_to_upgrading_ember
https://medium.com/ingenious/how-to-upgrade-ember-js-to-3-x-and-live-to-fight-another-day-cfc28c16b726
http://www.ember-cli-diff.org/
https://medium.com/front-end-hacking/everything-you-need-to-know-to-upgrade-your-ember-js-app-including-ember-3-9de5e808dde0
https://medium.com/ember-ish/upgrading-ember-from-1-13-to-2-8-0-f1dbcecc40ca
https://medium.com/front-end-hacking/how-to-use-ember-2-code-in-your-ember-3-app-9ed15c28bad6
Depending on the size of your application and how extensive your test suite is, you'll probably be dedicating a minimum of 4 weeks getting just the web version up to 3.5.
The process will be time consuming and tedious.
1. Upgrade by 1 minor version (1.12->1.13)
2: Run your test suite and fix any issues that come up
3: Manually test the tool by navigating around & fix any issues that come up
4: During the testing, you should have identified a handful of deprecations. Fix those.
5: Repeat steps 1-4
6: After you've upgraded to 2.0.0, you may be able to skip a couple of minor versions at a time, if you aren't using private APIs and your dependencies are small.
Ember maintains their [changelog](
https://github.com/emberjs/ember.js/blob/master/CHANGELOG.md) as well as a page that lists deprecations and their solutions, so you'll want to become buddies with the version you're upgrading to. For each deprecation they mention, check the linked issue history to see what the suggested replacement is. Be proactive - don't wait until the final version to fix a deprecation.
The big/common issues you'll encounter are:
Views are deprecated and removed. You'll need to understand how components work and migrate any existing views to a component.
The select helper gets removed.
If your views & components use targetObject to get the controller, you'll need to make them work without doing it. This means determining what properties & actions need to be passed in and explicitly doing it. Components shouldn't know anything about what called them.
Ember has a solid guide on working with deprecations at https://guides.emberjs.com/release/configuring-ember/handling-deprecations/ that may be of some help.
Keep your changes versioned. You'll break something bad enough that it's easier to just roll back and try again. If you're not using versioning, you're in for a really hard time.
Finally, make sure you clean out your npm directory between versions & wipes - If you don't, you may thing everything is working, but it really isn't.
As Patsy commented - You're probably better off hiring someone who knows ember very well to do this upgrade. If you don't know ember very well, you may be putting fixes in that back you into a corner.
I upgraded a bunch of Ember apps / addons from 1.11 -> 2.18 in advance of the 3.0 release. I don't think there was a single minor version upgrade until the 2.10s that didn't break my app.
I also simultaneously upgraded ember cli with the app. I tried upgrading ember cli to the latest, but I had a bunch of cryptic errors and reached a sort of dead end. What I instead opted for was looking back at the Ember release notes and seeing which version of ember cli was the latest at the time of the Ember release. I would upgrade Ember cli every 4 versions or so, unless if I encountered issues at which point I would immediately upgrade.
The single most important thing is automated tests. I see that you say you have no tests and will just manually test but this is foolish. I had a bunch of code that I needed to upgrade that had no tests. I wrote comprehensive tests over the course of a week since I had two weeks to do the upgrade. These were absolutely vital and some upgrades would break 60-80% of my tests. It would have taken me 2 months without tests probably, but I accomplished it in 2 weeks with the tests, using the first to write the needed extra tests.
Comprehensive tests are best, but far from necessary. At the minimum I would recommend you take the time to mock your API calls and write an acceptance test for each page of your app that serves as a smoke test. The test is as simple as go to the url and check the dom is there. Ember cli page object helps immensely + html5 test-* data classes.
Once you've done that, follow what #Trenton Trama suggested. Upgrade minor version, run tests, fix problems, rinse and repeat until fully upgraded.
I have just started learning Angular 2 through a tutorial.
I made a new project using ng new firstapp. Whenever I make changes to app.component.ts and save the file, the angular-cli always compiles successfully, displaying webpack: Compiled successfully.
However, sometimes it immediately reflects the changes in browser whilst most of the times it doesn't show any change. After I searched for the issue, someone suggested to try disabling the cache using Chrome developer tools but it didn't help. I am a beginner.
I am using WebStorm as my IDE. However when I made changes using SublimeText, the browser reflected the changes immediately. I guess it has got something to do with WebStorm. I'd like to carry on using WebStorm, as I love its features.
When using webpack-dev-server, it’s recommended to disable the IDE Safe write feature (Use "safe writes" (save changes to a temporary file first), Settings | Appearance & Behavior | System Settings ) , otherwise, the app won’t be updated on-time on changes. This issue is fixed in Webpack 2
In one of my solutions in javascripts files the intellisense suddenly stopped working.
All of the features are disabled - ctrl+space doesn't bring the list - like this
I took the print screen from another solution
and also the file looks like it was plain text -keywords has no colors.
I tried to open new solution and move the files there - still the same.
Files has intellisense only when I am debugging.
It feels like VS2010 see that those files are text files instead of js files.
It has something to do with tfs because it first happened to another member of the team and as soon as I took latest version of the solution - it happened to me.
When I create new js file - it looks fine , BUT after saving
the file , closing and reopen - again it is not colored
I found out that the problem is in one specific project - if I add js files to another project in the same solution it seems to be ok.
After some research and tests. This problem could be a couple of things:
Your file's extension is not .JS.
You are using an express edition.
You have not installed the Web Developer component on your installation (or removed it).
Let me know if this help you, If not I will look forward something else.
The complete reference about the JScript Intellisense on msdn:
http://msdn.microsoft.com/en-us/library/vstudio/bb385682(v=vs.100).aspx
As you can see in the image below, I just created a single javascript file in my Visual Studio 2010 with Web developers components and it is working:
So I solved this problem ....
I wanted to watch some value with QuickWatch (Shift+F9)
I got the message "Unable to evaluate the expression. The object invoked has disconnected from its clients." I pressed the green icon to refresh the values. After I closed the QuickWatch window I realized that I got the intellisense and highlighting back.
After a checkin to TFS, my colleague pulled the solution and got the intellisense and highlighting back as well.
Probably some weird bug in VS2010.