You can now officially use npm packages in your front-end page code!

Not sure what's wrong I've tried all possible imports(page as well as at backend/jwt) and none of them is working for me for stripe nodejs module - https://github.com/stripe/stripe-node .

Sample imports

import Stripe from "stripe"

import * from "stripe"

import Stripe from "node_modules/stripe"

......

Thanks @Anastasiia for the update (and the team for drilling through during this holiday season)!

Per the issue, I'm still getting similar error, where I tried:

• Reinstalling the npm package (v7.5.0 Apache-2.0)

• Tried importing the full package vs. features I need

My setup is:

//front-end code

import { authStateChanged } from 'backend/test'

$w.onReady(async function () {
let test = await authStateChanged()
console.log(test)
})


//backend/test.jsw
import 'firebase/auth'
var firebaseConfig = //some JSON from firebase

firebase.initializeApp(firebaseConfig)

export async function authStateChanged(){
return await firebase.auth().onAuthStateChanged(user => (user))
}

Please advise if I should be doing anything differently in the New Year :)

Best Regards,

Hey, @Asral

We are aware of the issue and I am pleased to inform you that our technical team has implemented a fix and we do not expect any further difficulties regarding this matter.

Can you please doublecheck if it works properly on your side and let us know?

Thanks in advance, we await for your reply.

@Aviv Fattal Does this also apply for firebase package? Had been trying to integrate phoneNumber authentication from firebase/auth from the backend. Any help would be much appreciated!

Concretely speaking, had tried these variations with same ModuleLoadError: Error loading web module backend/test.jsw: Cannot find the firebase namespace; be sure to include firebase-app.js before this library.

// non of the IMPORT variations worked...
// import 'firebase'
// import * as firebase from 'firebase/app'
// import 'firebase/auth'

// import * as firebase from 'firebase'
// import 'firebase/app'
// import 'firebase/auth'

// import * as firebase from 'firebase/app'
// import 'firebase/auth'


// non of the REQUIRE variations worked...
// require('firebase');
// var firebase = require('firebase/app')
// require('firebase/auth')

// var firebase = require('firebase');
// require('firebase/app')
// require('firebase/auth')

// var firebase = require('firebase/app')
// require('firebase/auth')


var firebaseConfig = //some JSON from firebase 
var app = firebase.initializeApp(firebaseConfig)
...  

I do have an HTML element implemented to bypass the current constraints, but it's still an 'ugly duck' solution :)

Thanks in advance!

Some that don't work in the frontend (as of yesterday):

mailgun-js

request

unirest

It means that available packages as listed here can now be used in your page code and not only in the backend files.

Do note that some packages only work in the backend or in the client. Make sure that you are using the package in the appropriate place.

Does that mean front-end packages such as https://www.npmjs.com/package/sharethis-reactjs which shows a share this page bar on the side.

Wow Wow! Good timing too.