Next-auth Package subpath '.providers/...' is not defined by "exports" in - next.js

Just got this error while working with Next-auth
Server Error
Error: Package subpath './providers/google' is not defined by "exports" in C:\Users...\node_modules\next-auth\package.json
Any help?

I think this comes from your next-auth version.
Make sure you're not working with mixed versions' features.
We now have two main versions: Version 3 and Version 4 (beta version).
By Reading the Docs, You can figure it out.
Check this Thread and use the Link to know more about this version issue
You can solve the problem by upgrading the Version 👉 Upgrade your Next-auth for some compatibilities issues

yes, I have the same issue as this, don't panic.
I solved just trying to install and reinstall node_module.
case 1 remove node_module and install again use npm (install success install not information error)
case 2 remove node_module again and install node_module use yarn ( I getting some information error for requiring version nodejs version), so in this case you need to upgrade or downgrade nodejs to another version.
okay that it, I hope this help you.

I had the same error, and in my particular case are be because i been running a old version of node.
first check your version of node
node -v
after upgrate with your package manager of your preference (brew, apt-get, etc)
brew upgrade node
and finally switch your version with a version manager tool of node
npm i -g n
n latest

for me updating the node version fixed the above issue

Try this:
import GoogleProvider from "next-auth/providers/google";

Related

Microsoft Visual C++ Runtime error - Assertion Failed

Using: VS Code
Working on: Running automation test scripts for WebdriverIO.
Error facing:
because of this error, my test specs are not executing. Is there any way to get rid of this??
Please follow the below steps to resolve this issue
Uninstall the current version of node.js.
Go to https://nodejs.org/en/blog/release/
Install the previous version of node.js (I installed from here 4.
https://nodejs.org/dist/v14.17.3/node-v14.17.3-x64.msi)
Restart your system
Try building the project using npm install
I hope this will solve your problem
The error here is coming from the Fibers npm package. Fibers only supports node versions before version 16. I had the same error message and switched the node version to 14.20.0 ,which is the newest LTS before version before 16 at the moment, and that solved the problem for me.

meteor version compatibility 1.1.0.3 vs 1.1.0.2

I got error message, running meteor 1.1.0.3
> ~/.meteor/meteor --version
Meteor 1.1.0.3
> ~/.meteor/meteor
Sorry, this project uses Meteor 1.1.0.2, which is not installed and could not be downloaded. Please check to make sure that you are online.
Shouldn't 1.1.0.3 be backward compatible? Can someone tell me how to get earlier version of Meteor
Meteor uses strict version requirements. So meteor-tool will try to download the exact version you specified in your project. If you are indeed not online and can't change that, or just want to start using the latest version that you seem to have installed, then just edit your .meteor/release file and manually change the meteor version to 1.1.0.3.

Meteor: How do you exactly install phantomJS?

There isn't a clear guide on how to install Phantom for Meteor, so I decided to ask a question to clarify things.
Do you have to install phantom binary in /usr/local/bin/? I downloaded a compiled phantomjs from the official website and placed inside the above path. I can run phantomjs from anywhere now because it's added to path.
In addition to 1, do you also have to install it from meteor npm? I followed this to install "phantomjs": "1.9.13" as a npm package inside my Meteor app. It gets confusing from here because the binary from the official website is v2.0.0 while the npm package is 1.9.13. Do I need to install both?
Because of the confusion in 2, I removed /usr/local/bin/phantomjs but then I can't run $phantomjs anywhere because I don't have anything in PATH.
My ultimate goal is to get spiderable working. What should I do?
Okay, the problem was the compiled phantomjs binary from the official webpage cannot be used right away in the latest Mac OS, but you have to unpack it first. To run spiderable package you don't need to do anything other than placing the binary file phantomjs inside your local path /usr/bin/local/. You can test this by running $phantomjs in your terminal. If you see phantomjs not found then you haven't installed it. If you see an error killed 9 then you have the same problem as mine, and you can solve it by following this.
You do not need the meteorhacks:npm package.
You can do this in two ways:
Method 1:
If you'd like to be able to use PhantomJS via your Meteor app, you would need to use the Meteorhacks NPM package and use the latest NPM version 1.9.16 I believe.
After that, you can edit your packages.json file to add "phantomjs": "1.9.16", and then reference it via var phantomjs = Meteor.npmRequire('phantomjs');
Method 2:
Alternatively, you can use the smart package for Meteor PhantomJS and give that a shot.
I personally feel like Method 1 is a better option, as that worked for me. I needed PhantomJS for an app, and that solution worked for me. I haven't tried Method 2 so I can't speak for it, but it looks promising as well.
Give them a shot, and let me know how it goes. Hope that helps!
Here is a phantomjs wrapper package from atmosphere: https://atmospherejs.com/gadicohen/phantomjs
More importantly here is the spiderable package:
https://atmospherejs.com/meteor/spiderable
I couldn't really answer the questions but more so point ya in a direction that I hope will solve your problem :)
In the terminal:
$ meteor npm install --save phantomjs
In your_meteor_app/server/main.js file (or wherever, provided it's server-side)
import phantom from 'phantom'
Just use npm:
//Global effect on your machine
npm install -g phantomjs
//Test if installed
npm list -g
//Test spiderable working correctly
Test spiderable

How to upgrade a meteor app from 0.9.4 to 1.0.0?

Meteor example app, microscope has version 0.9.4, when I try use meteor run command to launch application .
There have a print:
Sorry, this project uses Meteor METEOR#0.9.4, which is not installed and
could not be downloaded. Please check to make sure that you are online.
I am behind a proxy in corporate.
When I install the Meteor, only latest 1.0.0 can be installed.
How can I do?
Upgrade the app to 1.0.0, and how?
Downgrade the meteor to 0.9.4, and how?
I tried use meteor update --release 0.9.4, not work or using meteor update, other error pop up:
/home/hunter/.meteor/packages/meteor-tool/.1.0.35.hgbesu++os.linux.x86_32+web.browser+web.cordova/meteor-tool-os.linux.x86_32/dev_bundle/lib/node_modules/fibers/future.js:206
throw(ex);
..
Error: tunneling socket could not be established, cause=socket hang up
at Object.Future.wait (/home/hunter/.meteor/packages/meteor-tool/.1.0.35.hgbesu++os.linux.x86_32+web.browser+web.cordova/meteor-tool-os.linux.x86_32/dev_bundle/lib/node_modules/fibers/future.js:326:15)
at _.extend._createSocket (packages/ddp/stream_client_nodejs.js:265)
at _.extend._launchConnection (packages/ddp/stream_client_nodejs.js:142)
at new LivedataTest.ClientStream (packages/ddp/stream_client_nodejs.js:28)
at new Connection (packages/ddp/livedata_connection.js:52)
at Object.DDP.connect (packages/ddp/livedata_connection.js:1581)
This should proxy issue.
No document there after search.
I was able to successfully update a project from 0.9.3.1 to 1.1 with:
meteor update
Using meteor run like this:
meteor run --release
…won’t upgrade your meteor installation, but will download the --release and run the current app with it.
I had similar issue after updating meteor to 1.4.1. I happened to fix it with this help Github Issue
Reset your app
meteor reset
Install npm with meteor again
meteor npm install
Rebuild npm (Optional)
meteor npm rebuild
This is a bit late and slightly different: I have a similar problem when I upgraded from 1.0.3.1 to 1.0.3.2. After reading the answers here, and here, I tried the following which worked for me:
meteor update --release <new version>
replacing <new version> with the latest version you're running. This updated my project, and subsequent runs using meteor works as expected.
I was to update by change the file .meteor/release to meteor 1.0. I had packages issues, I also noticed that iron router inner actions changed (I fixed this by fixing the files load order) and on Meteor 1.0 you’ve a package for everything.
Try to add the package meteor-platform, it’s a meta package that contains the most used packages.
I also had issue with some atmosphere packages, it’s a tough job to upgrade it.

Iron Router doesn't update

I'm trying to update to the version 0.6.2, but when I insert mrt update iron-router in the command line I receive this alert:
Problem installing iron-router
✘ [0.6.1] conflicts with [0.6.2]
Can't resolve dependencies! Use --force if you don't mind mrt taking a wild guess and running your app anyway.
Am I doing something wrong?
Thanks in advance.
You could try a fresh installation:
meteor remove iron-router
rm -rf packages/iron-router
mrt update
meteor add iron-router
Also make sure you're using the latest version of meteorite
sudo -H npm install meteorite
It seems that one of the other smart packages you are using explicitly depends on a different version of Iron Router. Based on the smart.json packages that you posted, accounts-entry depends on 0.6.1 and I'm guessing you are manually depending on iron router 0.6.2 in your main app.
The best course of action is to probably change the version in accounts-entry (it will probably not break anything, as 0.6.1 to 0.6.2 was just bug fixes) and possibly submit a pull request for that as well.
Had a Similar problem.
Go to you app directory, open meteor, then open packages and you will see
iron-router
inside the file listed as a meteor package.
Then go to the terminal and
cd yourApp
meteor add iron:router
for me that added the 1x version and solved many of my errors.
Hope it works!

Resources